Triple
T16328466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourboulenc |
E396484
|
entity |
| Predicate | typicalStructureContribution |
P86921
|
FINISHED |
| Object | acidity in blends |
—
|
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: acidity in blends | Statement: [Bourboulenc, typicalStructureContribution, acidity in blends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStructureContribution Context triple: [Bourboulenc, typicalStructureContribution, acidity in blends]
-
A.
commonStructure
Indicates that two or more entities share the same or a very similar internal organization, pattern, or arrangement.
-
B.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
C.
typicalStructuralElement
chosen
Indicates that one entity is a standard or characteristic structural component commonly found within or forming part of another entity.
-
D.
contributionBase
Indicates the foundational amount, value, or resource on which a contribution, payment, or benefit is calculated or determined.
-
E.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dcd034819081d849003d918245 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.