Triple
T17551083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pol Roger |
E427463
|
entity |
| Predicate | usesBottleFermentation |
P127883
|
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: [Pol Roger, usesBottleFermentation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBottleFermentation Context triple: [Pol Roger, usesBottleFermentation, true]
-
A.
fermentationMethod
Indicates the process or technique by which a substance is fermented to achieve a desired transformation or product.
-
B.
primaryFermentationVessel
Indicates that one entity serves as the main container or vessel in which the primary fermentation process of another entity takes place.
-
C.
mustBeFermentedBy
Indicates that one entity is required to undergo a fermentation process carried out by another specified entity.
-
D.
possibleFermentationVessel
Indicates that something can serve as a suitable container or environment in which fermentation may take place.
-
E.
coFermentationAllowed
Indicates that multiple substances are permitted to be fermented together in a single combined fermentation process.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454656dc08190bba85b93bd07b0a2 |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.