Triple
T637890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelidonium |
E16664
|
entity |
| Predicate | hasLatexColor |
P18334
|
FINISHED |
| Object | yellow |
—
|
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: yellow | Statement: [Chelidonium, hasLatexColor, yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatexColor Context triple: [Chelidonium, hasLatexColor, yellow]
-
A.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
B.
hasFieldColor
Indicates that an entity possesses a field whose color is specified by another entity or value.
-
C.
hasRouteColorStandard
Indicates that a route is associated with a standardized color designation used for identification or classification.
-
D.
hasCrossColor
Indicates that an entity possesses a cross-shaped marking or pattern of a specified color.
-
E.
hasLiturgicalColor
Indicates that something is associated with a specific liturgical color used in religious rites or ceremonies.
- F. None of above. chosen
Provenance (4 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a4a1794a60819092b3dc3344426ed7 |
completed | March 1, 2026, 8:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.