Triple
T2934222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacDonnell Ranges |
E79225
|
entity |
| Predicate | hasColourCharacteristic |
P22465
|
FINISHED |
| Object | red-orange hues |
—
|
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: red-orange hues | Statement: [MacDonnell Ranges, hasColourCharacteristic, red-orange hues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColourCharacteristic Context triple: [MacDonnell Ranges, hasColourCharacteristic, red-orange hues]
-
A.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
B.
hasColourScheme
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
C.
hasColorPlay
Indicates a relationship where something exhibits or incorporates playful or varied use of color.
-
D.
hasColoration
chosen
Indicates that an entity possesses a particular color or pattern of colors.
-
E.
hasRGB
Indicates that an entity possesses or is associated with a specific RGB (red, green, blue) color value.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983b65f881909b8b7d3dc5c224fd |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.