Triple
T28558005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swimming Pool cocktail |
E723057
|
entity |
| Predicate | hasPrimarySpirit |
P14782
|
FINISHED |
| Object | vodka |
—
|
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: vodka | Statement: [Swimming Pool cocktail, hasPrimarySpirit, vodka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySpirit Context triple: [Swimming Pool cocktail, hasPrimarySpirit, vodka]
-
A.
hasSecondarySpirit
Indicates that an entity is associated with an additional, subordinate, or supporting spirit beyond its primary one.
-
B.
primarySpirit
chosen
Indicates that one entity is the main or most fundamental spiritual essence associated with another entity.
-
C.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
-
D.
hasSpiritualPresence
Indicates that an entity possesses, embodies, or exerts a non-physical, spiritual influence or presence in relation to another entity or context.
-
E.
hasSpiritualDimension
Indicates that something possesses or involves a non-material, spiritual, or transcendent aspect or quality.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: April 28, 2026, 3:47 a.m.