Triple
T22197680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lohrasp |
E548588
|
entity |
| Predicate | chronologicalPositionInEpic |
P23880
|
FINISHED |
| Object | after Kay Khosrow and before Goshtasp |
—
|
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: after Kay Khosrow and before Goshtasp | Statement: [Lohrasp, chronologicalPositionInEpic, after Kay Khosrow and before Goshtasp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInEpic Context triple: [Lohrasp, chronologicalPositionInEpic, after Kay Khosrow and before Goshtasp]
-
A.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
C.
chronologicalPositionInLabors
Indicates the specific order or sequence in which a given labor occurs within a defined series of labors.
-
D.
chronologicalOrderInSeries
chosen
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
E.
rankWithinChapter
Indicates the relative ordering or position of an item among other items within the same chapter.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae8c74c819080c7f9e8383ecaa7 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.