Triple
T33083109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid M |
E846558
|
entity |
| Predicate | inspiredLaterLocation |
P185675
|
FINISHED |
| Object | Utopia |
—
|
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: Utopia | Statement: [Asteroid M, inspiredLaterLocation, Utopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredLaterLocation Context triple: [Asteroid M, inspiredLaterLocation, Utopia]
-
A.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
B.
immediateAftermathLocation
Indicates the location where the direct and immediate consequences of an event take place.
-
C.
plannedLocation
Indicates the intended or scheduled location where an entity is expected to be or an event is planned to occur.
-
D.
unveiledLocation
Indicates that an entity has revealed or made known the location of another entity or object.
-
E.
laterUseLocation
Indicates that an entity is located at a place where it will be used or utilized at a later time.
- F. None of above. chosen
Provenance (4 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 1, 2026, 1:26 a.m.