Triple
T25949426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancients |
E653927
|
entity |
| Predicate | laterHomeworld |
P59198
|
FINISHED |
| Object | Earth (Milky Way) |
—
|
NE NERFINISHED |
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: Earth (Milky Way) | Statement: [Ancients, laterHomeworld, Earth (Milky Way)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHomeworld Context triple: [Ancients, laterHomeworld, Earth (Milky Way)]
-
A.
homeworldLost
Indicates that an entity has lost its original homeworld, typically through destruction, abandonment, or irreversible separation.
-
B.
adoptedHomeworld
Indicates that an entity has chosen or taken on a particular world as its primary place of residence or affiliation, distinct from its place of origin.
-
C.
laterTerritory
chosen
Indicates that one territory is a subsequent or successor territory to another in time.
-
D.
homePlanet
Indicates the planet that serves as the native or original world of an entity.
-
E.
homeworldLocation
Indicates the relationship between an entity and the specific place or celestial body that serves as its homeworld.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 22, 2026, 8:43 a.m.