Triple
T31704094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Cru Supérieur (for Sauternes) |
E809133
|
entity |
| Predicate | onlyEstateInRank |
P102190
|
FINISHED |
| Object | Château d’Yquem |
—
|
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: Château d’Yquem | Statement: [Premier Cru Supérieur (for Sauternes), onlyEstateInRank, Château d’Yquem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlyEstateInRank Context triple: [Premier Cru Supérieur (for Sauternes), onlyEstateInRank, Château d’Yquem]
-
A.
isOnlyEstateWithRank
chosen
Indicates that an estate is the sole estate possessing a particular rank, with no other estate sharing that same rank.
-
B.
rankRestriction
Indicates a constraint or limit placed on the rank or hierarchical level that an entity may hold within a given system or structure.
-
C.
nobleEstate
Indicates that an entity is a noble’s estate or property associated with nobility.
-
D.
hasRankByArea
Indicates that something is assigned a position or ranking based on its area size.
-
E.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:13 p.m.