Triple
T9593661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1855 Bordeaux classification |
E231478
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical ranking |
C26798
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical ranking Context triple: [1855 Bordeaux classification, instanceOf, historical ranking]
-
A.
historical position
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
B.
power ranking
A power ranking is an ordered list that subjectively rates entities (such as teams, players, or products) based on their perceived current strength or performance relative to one another.
-
C.
historical military rank
A historical military rank is a formally defined level of authority and responsibility within past armed forces, reflecting the hierarchical structure, duties, and social status of military personnel in a specific historical context.
-
D.
sports ranking system
A sports ranking system is a structured method for evaluating and ordering teams or athletes based on performance metrics, results, and predefined rules to determine relative standings.
-
E.
SS rank
SS rank is a conceptual class representing an elite, top-tier rating or classification that surpasses standard ranking levels, often used to denote exceptional performance or quality.
- F. None of above. chosen
Provenance (1 batch)
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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:07 p.m.