Triple
T26880347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domaine Jean Grivot |
E676874
|
entity |
| Predicate | oakRegime |
P119035
|
FINISHED |
| Object | mix of new and used 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: mix of new and used oak | Statement: [Domaine Jean Grivot, oakRegime, mix of new and used oak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oakRegime Context triple: [Domaine Jean Grivot, oakRegime, mix of new and used oak]
-
A.
oakRegimen
Indicates a prescribed or customary course of actions, treatments, or behaviors associated with the entity referred to as "oak."
-
B.
oakAffinity
Indicates a special connection, preference, or strong association between an entity and oak (such as oak trees, wood, or oak-related environments).
-
C.
oakTypeUsed
chosen
Indicates that a particular type of oak is used in relation to another entity, such as in construction, manufacturing, or production.
-
D.
oakBranchRepresents
Indicates that an oak branch symbolically stands for, signifies, or serves as an emblem of something else.
-
E.
oakAgingTypical
Indicates that it is typical or customary for something (such as a product, especially a beverage) to undergo aging in oak.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f1c9c888190a3b8711c2d35036b |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:38 a.m.