Triple
T31704015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Grand Cru Classé B |
E809131
|
entity |
| Predicate | notTopmostTier |
P172447
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Premier Grand Cru Classé B, notTopmostTier, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notTopmostTier Context triple: [Premier Grand Cru Classé B, notTopmostTier, true]
-
A.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
B.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
C.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
-
D.
hasSiblingTier
Indicates that two entities occupy the same or equivalent sibling level or rank within a hierarchical structure.
-
E.
hasTierStructure
Indicates that something is organized into distinct hierarchical levels or layers within a structured system.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:13 p.m.