Triple
T1106125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashoka Chakra |
E25490
|
entity |
| Predicate | ISOColorSpecification |
P60
|
FINISHED |
| Object | navy blue (same as the blue in the Indian flag) |
—
|
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: navy blue (same as the blue in the Indian flag) | Statement: [Ashoka Chakra, ISOColorSpecification, navy blue (same as the blue in the Indian flag)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOColorSpecification Context triple: [Ashoka Chakra, ISOColorSpecification, navy blue (same as the blue in the Indian flag)]
-
A.
colorEncoding
Indicates how the color information of an entity is represented, formatted, or encoded.
-
B.
colors
chosen
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
C.
colorEncodingMethod
Indicates the method or scheme used to represent or encode color information.
-
D.
colorVarietyOf
Indicates that one entity represents a specific color variant or color option of another entity.
-
E.
hasFilmColorType
Indicates that a film is associated with a particular color process or color classification (e.g., color, black-and-white).
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e339f88190afc027216e95d2f7 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.