Triple
T28057242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sons of Jesse |
E708999
|
entity |
| Predicate | locatedInNarrativeSetting |
P9801
|
FINISHED |
| Object | Bethlehem in Judah |
—
|
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: Bethlehem in Judah | Statement: [sons of Jesse, locatedInNarrativeSetting, Bethlehem in Judah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNarrativeSetting Context triple: [sons of Jesse, locatedInNarrativeSetting, Bethlehem in Judah]
-
A.
locationOfNarrative
chosen
Indicates the place or setting where the events or story described in the narrative occur.
-
B.
placeOfSetting
Indicates the location or environment where an event, scene, or situation takes place.
-
C.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
-
D.
occupiesNarrativeSpace
Indicates that an entity takes up or is present within a particular portion or region of a narrative’s structure or progression.
-
E.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 27, 2026, 8:37 p.m.