Triple
T3103408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Founding of the Order of the Garter |
E64772
|
entity |
| Predicate | hasAssociatedColor |
P18249
|
FINISHED |
| Object | blue |
—
|
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: blue | Statement: [Founding of the Order of the Garter, hasAssociatedColor, blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedColor Context triple: [Founding of the Order of the Garter, hasAssociatedColor, blue]
-
A.
hasColorReference
Indicates that one entity serves as a reference or source for determining or specifying the color associated with another entity.
-
B.
hasColorSymbol
chosen
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
C.
hasComplementaryColor
Indicates that one color is the complementary (i.e., opposite on the color wheel, providing maximum contrast) counterpart of another color.
-
D.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
E.
hasColorProcess
Indicates a relationship where an entity is associated with a specific method or process used to apply, change, or manage its color.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada26f376c8190a049399e33314d52 |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.