Triple
T278668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KG |
E5304
|
entity |
| Predicate | orderRank |
P1944
|
FINISHED |
| Object | highest order of chivalry in the United Kingdom |
—
|
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: highest order of chivalry in the United Kingdom | Statement: [KG, orderRank, highest order of chivalry in the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderRank Context triple: [KG, orderRank, highest order of chivalry in the United Kingdom]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankedAs
chosen
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
C.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
D.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
-
E.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dee7830819087f153769a8496b9 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.