Triple
T3178890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight Grand Commander |
E66530
|
entity |
| Predicate | orderPrecedenceWithinOrder |
P1803
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Knight Grand Commander, orderPrecedenceWithinOrder, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderPrecedenceWithinOrder Context triple: [Knight Grand Commander, orderPrecedenceWithinOrder, 1]
-
A.
orderPrecedence
chosen
Indicates that one entity must come before another in a defined sequence or priority order.
-
B.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
orderHierarchy
Indicates a hierarchical ordering relationship where one entity is positioned above or below another in a structured sequence or chain of command.
-
D.
orderPrecedenceInCanada
Indicates the relative legal or procedural priority that one item holds over another specifically within the Canadian context.
-
E.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69db2088190baa1305892eb148a |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.