Triple
T32219278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | engolpion |
E823018
|
entity |
| Predicate | hasTypicalWearerRank |
P7007
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [engolpion, hasTypicalWearerRank, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalWearerRank Context triple: [engolpion, hasTypicalWearerRank, bishop]
-
A.
wearerRankRange
Indicates the range of ranks that an individual must fall within in order to be permitted or intended to wear a specified item.
-
B.
wearerRankCategory
Indicates the classification of the wearer's rank into a broader rank category (e.g., junior, senior, officer, etc.) within a ranking system.
-
C.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
D.
wearerMust
Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
-
E.
wearerEntitlement
Indicates that an entity has the right or authorization to wear a particular item (such as clothing, equipment, or an accessory).
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 1, 2026, 12:38 a.m.