Triple
T17815474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Order of Orange-Nassau |
E444825
|
entity |
| Predicate | hasEnamelColor |
P22465
|
FINISHED |
| Object | white enamel cross with orange and blue elements |
—
|
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: white enamel cross with orange and blue elements | Statement: [Commander of the Order of Orange-Nassau, hasEnamelColor, white enamel cross with orange and blue elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnamelColor Context triple: [Commander of the Order of Orange-Nassau, hasEnamelColor, white enamel cross with orange and blue elements]
-
A.
hasPigment
Indicates that one entity contains, incorporates, or is characterized by a particular pigment.
-
B.
hasFacePaintColor
Indicates that an entity’s face paint is of a specified color.
-
C.
hasCapColor
Indicates that an entity possesses a cap whose color is specified by the related value.
-
D.
hasColoration
chosen
Indicates that an entity possesses a particular color or pattern of colors.
-
E.
hasFleshColor
Indicates that an entity possesses a particular color or characteristic of its flesh or internal tissue.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887e80688190a2ac3308b0e815c6 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.