Triple
T20721447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laphroaig Lore |
E509322
|
entity |
| Predicate | coloringAdded |
P132018
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Laphroaig Lore, coloringAdded, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coloringAdded Context triple: [Laphroaig Lore, coloringAdded, no]
-
A.
coloredBy
chosen
Indicates that one entity serves as the source, agent, or cause of the color or coloration of another entity.
-
B.
colorTincture
Indicates that one entity has a specific heraldic color or tincture applied to it.
-
C.
colorationFunction
Indicates a relationship where an entity’s coloration serves a particular role or purpose, such as camouflage, signaling, or protection.
-
D.
colorCharge
Indicates a relationship where an entity possesses a specific quantum color charge (such as red, green, or blue) in the context of strong nuclear interactions.
-
E.
isColorCharged
Indicates that an entity possesses color charge, meaning it carries the type of charge associated with the strong nuclear interaction in quantum chromodynamics.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d5eec08190832ffba8a90f3076 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:27 p.m.