Triple
T27219147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads Motel |
E681221
|
entity |
| Predicate | narrativeLocationFor |
P9801
|
FINISHED |
| Object | drama in Crossroads (TV series) |
—
|
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: drama in Crossroads (TV series) | Statement: [Crossroads Motel, narrativeLocationFor, drama in Crossroads (TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeLocationFor Context triple: [Crossroads Motel, narrativeLocationFor, drama in Crossroads (TV series)]
-
A.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
-
B.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
-
C.
narrativeLocationRelativeToCamelot
Indicates the spatial or contextual position of a narrative’s events relative to Camelot.
-
D.
narrativeEndPoint
Indicates the point in a narrative sequence at which the story or described event concludes or reaches its final state.
-
E.
plotLocation
Indicates the relationship between a creative work and the place or setting where its story or events occur.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 9:42 a.m.