Triple
T5020671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banyuls AOC |
E112840
|
entity |
| Predicate | fermentationStoppedBy |
P11350
|
FINISHED |
| Object | addition of neutral grape spirit |
—
|
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: addition of neutral grape spirit | Statement: [Banyuls AOC, fermentationStoppedBy, addition of neutral grape spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fermentationStoppedBy Context triple: [Banyuls AOC, fermentationStoppedBy, addition of neutral grape spirit]
-
A.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
B.
halted
Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
-
C.
hasStop
Indicates that something (such as a route, service, or journey) includes or is associated with a particular stop or stopping point.
-
D.
activityEndedBecauseOf
Indicates that an activity has come to an end specifically due to a particular cause, condition, or event.
-
E.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736399ac8190aa38efc4b4edc6a2 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.