Triple
T5733235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lorne |
E126435
|
entity |
| Predicate | rankRelativeToDuke |
P9684
|
FINISHED |
| Object | lower |
—
|
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: lower | Statement: [Lord Lorne, rankRelativeToDuke, lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankRelativeToDuke Context triple: [Lord Lorne, rankRelativeToDuke, lower]
-
A.
rankRelativeToPeerage
chosen
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
B.
rankBeforeKingship
Indicates that one entity held a higher or earlier rank or status than another entity prior to that other entity attaining kingship.
-
C.
rankInPrincelyOrder
Indicates the position or level an entity holds within a specified princely order or hierarchy.
-
D.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
E.
establishedAsDukes
Indicates that certain individuals or entities were formally created or recognized with the rank and title of dukes.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.