Triple
T28557996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Lagoon (cocktail) |
E723056
|
entity |
| Predicate | containsSpiritType |
P14786
|
FINISHED |
| Object | neutral 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: neutral spirit | Statement: [Blue Lagoon (cocktail), containsSpiritType, neutral spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpiritType Context triple: [Blue Lagoon (cocktail), containsSpiritType, neutral spirit]
-
A.
typeOfSpirit
Indicates the specific kind or category of spirit (e.g., ghost, demon, angel) that an entity belongs to.
-
B.
baseSpiritType
chosen
Indicates the type or category of the primary alcoholic spirit that serves as the base in a drink or spirit product.
-
C.
hasSpiritSymbolRole
Indicates that an entity serves in a designated role or function specifically associated with a spirit symbol.
-
D.
recognizesSpirit
Indicates that one entity acknowledges, identifies, or affirms the spiritual nature, presence, or authority of another entity.
-
E.
hasSpiritualHead
Indicates that one entity serves as the primary religious or spiritual leader or authority for another entity.
- 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_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 28, 2026, 3:47 a.m.