Triple
T4922427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vashti |
E110495
|
entity |
| Predicate | orderInNarrative |
P47025
|
FINISHED |
| Object | first queen mentioned in Book of Esther |
—
|
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: first queen mentioned in Book of Esther | Statement: [Vashti, orderInNarrative, first queen mentioned in Book of Esther]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInNarrative Context triple: [Vashti, orderInNarrative, first queen mentioned in Book of Esther]
-
A.
placeInSuccessionNarrative
chosen
Indicates the position or order an entity occupies within a sequence of events or elements in a narrative.
-
B.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
C.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
D.
chronologicalOrderInSeries
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
E.
locationOfNarrative
Indicates the place or setting where the events or story described in the narrative 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.