Triple
T29928061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vespra |
E760137
|
entity |
| Predicate | chronologicalOrderInWork |
P23880
|
FINISHED |
| Object | first part |
—
|
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 part | Statement: [Vespra, chronologicalOrderInWork, first part]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalOrderInWork Context triple: [Vespra, chronologicalOrderInWork, first part]
-
A.
chronologicalOrderInSeries
chosen
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
B.
chronologicalOrderInComplex
Indicates that one event or element occurs at a specific position within a more complex, ordered temporal sequence relative to other events or elements.
-
C.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
D.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
E.
chronologicalOrderInSagas
Indicates that the referenced sagas are arranged according to the sequence of events in their internal story chronology, rather than by publication or release order.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 29, 2026, 6:17 p.m.