Triple
T31723411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troisième Cru Classé |
E809644
|
entity |
| Predicate | appliesPrimarilyToSubregion |
P197026
|
FINISHED |
| Object | Médoc |
—
|
NE NERFINISHED |
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: Médoc | Statement: [Troisième Cru Classé, appliesPrimarilyToSubregion, Médoc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesPrimarilyToSubregion Context triple: [Troisième Cru Classé, appliesPrimarilyToSubregion, Médoc]
-
A.
appliesToCountrySubdivision
Indicates that something (such as a rule, measure, or attribute) is specifically applicable to a particular administrative subdivision within a country (e.g., a state, province, or region).
-
B.
inCountrySubregion
Indicates that one location or entity is situated within a specific subregion of a country.
-
C.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
-
D.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
E.
subnationalRegion
Indicates that one region is a subdivision or administrative part of a larger nation or country.
- F. None of above. chosen
Provenance (4 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_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: April 30, 2026, 11:19 p.m.