Triple
T28718499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Elysium universe) |
E730025
|
entity |
| Predicate | countryFilmingLocationForDepiction |
P21831
|
FINISHED |
| Object | Mexico |
—
|
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: Mexico | Statement: [Earth (Elysium universe), countryFilmingLocationForDepiction, Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryFilmingLocationForDepiction Context triple: [Earth (Elysium universe), countryFilmingLocationForDepiction, Mexico]
-
A.
formerFilmingLocation
Indicates that a place was once used as a filming location for a work but is no longer used for that purpose.
-
B.
filmingLocationContext
Indicates the contextual relationship specifying where the filming of an event, scene, or production took place.
-
C.
filmingLocationForAdaptation
Indicates the place where an adaptation (such as a film or TV version of a work) was shot or recorded.
-
D.
countryOfFilming
chosen
Indicates the country where the filming or production of a work physically took place.
-
E.
filmLocationFor
Indicates a relationship where a specific place serves as the filming location for a particular film or production.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: April 28, 2026, 5:52 a.m.