Triple
T3432091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hautdesert |
E72361
|
entity |
| Predicate | narrativeLocationRelativeToCamelot |
P48216
|
FINISHED |
| Object | distant from Camelot |
—
|
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: distant from Camelot | Statement: [Hautdesert, narrativeLocationRelativeToCamelot, distant from Camelot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeLocationRelativeToCamelot Context triple: [Hautdesert, narrativeLocationRelativeToCamelot, distant from Camelot]
-
A.
locationOfNarrative
Indicates the place or setting where the events or story described in the narrative occur.
-
B.
knightingLocation
Indicates the place where a knighting ceremony or act of conferring knighthood occurs.
-
C.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
D.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
E.
locationOfPassage
Indicates the place or area through which a passage, route, or transit occurs or is situated.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9c077d48190bee40795cab3e422 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:15 p.m.