Triple
T17551073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pol Roger |
E427463
|
entity |
| Predicate | agingOnLees |
P106684
|
FINISHED |
| Object | extended |
—
|
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: extended | Statement: [Pol Roger, agingOnLees, extended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agingOnLees Context triple: [Pol Roger, agingOnLees, extended]
-
A.
agingRequirementOnLees
Indicates that an entity must be aged in contact with its lees (sediment of dead yeast and other particles) for a specified period as part of a production or quality requirement.
-
B.
maturationOnLees
chosen
Indicates a process where a substance, typically a beverage like wine, matures or ages while remaining in contact with its lees (sediment of dead yeast and other particles).
-
C.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
D.
engagementTo
Indicates a formal promise or commitment between two entities to enter into a future partnership or binding relationship.
-
E.
agingCommon
Indicates that the entities share a common or typical pattern, process, or characteristic related to aging.
- 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_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. |
Created at: April 10, 2026, 5:50 a.m.