Triple
T22517437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABC Extra Stout |
E556683
|
entity |
| Predicate | isConsumedOnOccasion |
P14780
|
FINISHED |
| Object | social gatherings |
—
|
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: social gatherings | Statement: [ABC Extra Stout, isConsumedOnOccasion, social gatherings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsumedOnOccasion Context triple: [ABC Extra Stout, isConsumedOnOccasion, social gatherings]
-
A.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
B.
eatenOnOccasion
chosen
Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
-
C.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
D.
isConsumedBy
Indicates that one entity is eaten, drunk, or otherwise ingested or used up by another entity.
-
E.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2df59c81909c4ae2f20f1cbb32 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.