Triple
T34966991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highest Duty |
E1008426
|
entity |
| Predicate | placeOfNarrativeEvent |
P9801
|
FINISHED |
| Object | Hudson River |
—
|
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: Hudson River | Statement: [Highest Duty, placeOfNarrativeEvent, Hudson River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfNarrativeEvent Context triple: [Highest Duty, placeOfNarrativeEvent, Hudson River]
-
A.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
-
B.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
C.
placeOfFictionalEvent
Indicates the location where a fictional event is depicted as occurring within a narrative or story.
-
D.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
-
E.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4 p.m.