Triple
T38541581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Moon |
E924845
|
entity |
| Predicate | isFlavoredWith |
P149822
|
FINISHED |
| Object | orange peel |
—
|
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: orange peel | Statement: [Blue Moon, isFlavoredWith, orange peel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFlavoredWith Context triple: [Blue Moon, isFlavoredWith, orange peel]
-
A.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to another entity.
-
B.
isFlavouredVariantOf
Indicates that one item is a version of another that has been modified or distinguished specifically by added or altered flavor characteristics.
-
C.
isOfficialFlavorOf
Indicates that one item is formally recognized or designated as an official flavor associated with another entity (such as a brand, product line, or event).
-
D.
hasSecondaryFlavor
Indicates that an entity possesses an additional, subordinate flavor characteristic beyond its primary flavor.
-
E.
hasFlavorContent
chosen
Indicates that something possesses or contains a particular flavor or set of flavor characteristics.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2eb85e4819088eb5a8fc4d4f668 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.