Triple
T11018873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Préludes (Book I) |
E260433
|
entity |
| Predicate | hasOrderingPrinciple |
P88387
|
FINISHED |
| Object | non-chronological by key |
—
|
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: non-chronological by key | Statement: [Préludes (Book I), hasOrderingPrinciple, non-chronological by key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderingPrinciple Context triple: [Préludes (Book I), hasOrderingPrinciple, non-chronological by key]
-
A.
hasOrderingMethod
chosen
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
B.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
-
C.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
D.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
E.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a9e8788190a0f45b52bad1bfb5 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.