Triple
T12347188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crémant de Loire |
E294384
|
entity |
| Predicate | wholeBunchPressingRequired |
P104595
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Crémant de Loire, wholeBunchPressingRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wholeBunchPressingRequired Context triple: [Crémant de Loire, wholeBunchPressingRequired, yes]
-
A.
controlledPress
Indicates that one entity exerts influence over or directs the activities and output of a press or media organization.
-
B.
requiresEnsemble
Indicates that performing or realizing one entity necessitates the coordinated participation of multiple entities acting together as an ensemble.
-
C.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
D.
heldMany
Indicates that one entity has possessed or maintained control over a large number or quantity of another entity over time.
-
E.
mustTouch
Indicates that the entities are required to be in direct physical contact with each other.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.