Triple
T31656276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New New York City |
E807865
|
entity |
| Predicate | locatedOnInFiction |
P199044
|
FINISHED |
| Object | Earth |
E687
|
NE 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: Earth | Statement: [New New York City, locatedOnInFiction, Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnInFiction Context triple: [New New York City, locatedOnInFiction, Earth]
-
A.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
B.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
C.
locatedNearFiction
Indicates that one fictional entity or place is situated close to another within an imagined or narrative context.
-
D.
locatedInFictionalEvent
Indicates that one entity (typically a place, object, or character) exists or occurs within the context or setting of a fictional event.
-
E.
basedInFiction
chosen
Indicates that an entity is located or primarily situated within a fictional setting, universe, or narrative world.
- F. None of above.
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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79e7084c8190824fc5cdfaa1fd35 |
completed | June 12, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
Created at: April 30, 2026, 10:55 p.m.