Triple
T31723417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troisième Cru Classé |
E809644
|
entity |
| Predicate | relativeRankInClassification |
P152574
|
FINISHED |
| Object | third tier |
—
|
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: third tier | Statement: [Troisième Cru Classé, relativeRankInClassification, third tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeRankInClassification Context triple: [Troisième Cru Classé, relativeRankInClassification, third tier]
-
A.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
B.
classRank
Indicates the relative academic standing or position of an entity within a class or cohort based on performance or criteria.
-
C.
rankIn
chosen
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
D.
attendanceRank
Indicates the relative position or level of an entity in terms of how frequently or consistently it attends compared to others.
-
E.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:19 p.m.