Triple
T32485737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannah Khoury |
E830234
|
entity |
| Predicate | hasStoryLocation |
P9801
|
FINISHED |
| Object | New Orleans field office |
—
|
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: New Orleans field office | Statement: [Hannah Khoury, hasStoryLocation, New Orleans field office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStoryLocation Context triple: [Hannah Khoury, hasStoryLocation, New Orleans field office]
-
A.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
B.
hasStoryPath
Indicates that there exists a defined narrative route or sequence of events connecting one entity to another within a story or interactive experience.
-
C.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
-
D.
storyTakesPlaceOver
Indicates that a story unfolds across or spans a specified duration of time.
-
E.
homeLocationInStory
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 1, 2026, 12:58 a.m.