Triple
T29119902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solarians |
E737149
|
entity |
| Predicate | attitudeTowardOtherSpacers |
P159371
|
FINISHED |
| Object | aloof |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: aloof | Statement: [Solarians, attitudeTowardOtherSpacers, aloof]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attitudeTowardOtherSpacers Context triple: [Solarians, attitudeTowardOtherSpacers, aloof]
-
A.
attitudeTowardEarthmen
Indicates the stance, feelings, or disposition that one entity holds toward Earthmen.
-
B.
attitudeTowardOthers
chosen
Indicates the nature or disposition of one entity’s feelings, judgments, or behavioral stance toward other entities.
-
C.
attitudeTowardEnemy
Indicates the stance, feelings, or disposition that one entity holds toward an opposing or hostile entity.
-
D.
spacePolarity
Indicates a relationship where one entity’s spatial orientation, charge, or directional attribute is contrasted or opposed to another’s within a defined space.
-
E.
inUniverseAttitude
Indicates the stance, feelings, or perspective that an entity holds toward something within the context of a specific fictional or defined universe.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11:24 a.m.