Triple
T5611642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartmouth green |
E147370
|
entity |
| Predicate | hasSaturation |
P48842
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Dartmouth green, hasSaturation, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaturation Context triple: [Dartmouth green, hasSaturation, high]
-
A.
hasRGB
Indicates that an entity possesses or is associated with a specific RGB (red, green, blue) color value.
-
B.
supportsColorSampling
Indicates that one entity can perform or accommodate color sampling operations on another entity or its data.
-
C.
hasColorExcess
Indicates that an entity exhibits a measured amount of color excess, typically representing the difference between its observed color and its intrinsic or expected color.
-
D.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
-
E.
hasColorInfo
chosen
Indicates that an entity is associated with specific color-related information or attributes.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0211fad448190b068b77ed25931d5 |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.