Triple
T26795100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treble X |
E670923
|
entity |
| Predicate | associatedWithUniformColour |
P65875
|
FINISHED |
| Object | cherry-coloured overalls of the 11th Hussars |
—
|
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: cherry-coloured overalls of the 11th Hussars | Statement: [Treble X, associatedWithUniformColour, cherry-coloured overalls of the 11th Hussars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithUniformColour Context triple: [Treble X, associatedWithUniformColour, cherry-coloured overalls of the 11th Hussars]
-
A.
associatedColour
chosen
Indicates that one entity is linked to another as its characteristic or representative colour.
-
B.
usedUniformColor
Indicates that multiple entities share or employed the same uniform color in a given context.
-
C.
areUniform
Indicates that all elements in a given set or collection share the same value, property, or characteristic.
-
D.
uniformColorFeature
Indicates that the related entities share or exhibit the same uniform color characteristic.
-
E.
usesUniform
Indicates that one entity regularly wears or employs a standardized set of clothing or equipment designated as a uniform.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: April 27, 2026, 4:19 a.m.