Triple
T6398959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miramar (film) |
E144010
|
entity |
| Predicate | mainLocationInStory |
P9801
|
FINISHED |
| Object | pension in Alexandria |
—
|
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: pension in Alexandria | Statement: [Miramar (film), mainLocationInStory, pension in Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLocationInStory Context triple: [Miramar (film), mainLocationInStory, pension in Alexandria]
-
A.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
-
B.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
C.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
D.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
-
E.
narrativeLocationRelativeToCamelot
Indicates the spatial or contextual position of a narrative’s events relative to Camelot.
- 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_69c008dc56fc81908d43ffcc11d73bdd |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06897ebc48190842d48cce469eba5 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.