Triple
T9727829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Haut-Bailly |
E235659
|
entity |
| Predicate | notableVintage |
P33056
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Château de Haut-Bailly, notableVintage, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVintage Context triple: [Château de Haut-Bailly, notableVintage, 2000]
-
A.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
B.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
C.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
-
D.
notableEditionYear
chosen
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
E.
catalogueNote
Indicates that there is a descriptive or administrative note recorded about an item within a catalogue or cataloguing process.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e7af544819090a8a1adec41943c |
completed | April 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:21 p.m.