Triple
T13388928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château La Fleur-Pétrus |
E319519
|
entity |
| Predicate | oakRegimen |
P109722
|
FINISHED |
| Object | partly new oak |
—
|
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: partly new oak | Statement: [Château La Fleur-Pétrus, oakRegimen, partly new oak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oakRegimen Context triple: [Château La Fleur-Pétrus, oakRegimen, partly new oak]
-
A.
oakAffinity
Indicates a special connection, preference, or strong association between an entity and oak (such as oak trees, wood, or oak-related environments).
-
B.
sacredTree
Indicates that an entity is regarded as a sacred or holy tree within a religious, spiritual, or cultural context.
-
C.
typicalOakAroma
Indicates that something has the characteristic smell commonly associated with oak wood or oak aging.
-
D.
oakAgingTypical
Indicates that it is typical or customary for something (such as a product, especially a beverage) to undergo aging in oak.
-
E.
oakBranchRepresents
Indicates that an oak branch symbolically stands for, signifies, or serves as an emblem of something else.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d3a40081909ba49556130ad0e7 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:34 p.m.