Triple
T37205824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kornephoros |
E922165
|
entity |
| Predicate | colorIndexUminusB |
P63031
|
FINISHED |
| Object | ~0.63 |
—
|
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: ~0.63 | Statement: [Kornephoros, colorIndexUminusB, ~0.63]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorIndexUminusB Context triple: [Kornephoros, colorIndexUminusB, ~0.63]
-
A.
hasUminusBColorIndex
chosen
Indicates that there is a specified U−B color index value characterizing the color difference between two photometric bands in a subject.
-
B.
colorIndexB−V
Indicates the difference between an object's blue (B) and visual (V) magnitudes, representing its color and thus its temperature or spectral characteristics.
-
C.
hasColorIndexB-R
Indicates that one entity has a specified B–R color index value, representing the difference between its blue and red magnitudes.
-
D.
CIE1964uvChromaticity_u
Indicates the u coordinate of an entity’s chromaticity in the CIE 1964 uv color space.
-
E.
colorComponent
Indicates that one entity is a component or constituent part of the overall color of another entity.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:15 p.m.