Triple
T21990378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIE 1931 XYZ |
E543065
|
entity |
| Predicate | XRepresents |
P128000
|
FINISHED |
| Object | red–green opponent content (non-physiological) |
—
|
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–green opponent content (non-physiological) | Statement: [CIE 1931 XYZ, XRepresents, red–green opponent content (non-physiological)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: XRepresents Context triple: [CIE 1931 XYZ, XRepresents, red–green opponent content (non-physiological)]
-
A.
entityRepresents
chosen
Indicates that one entity stands for, symbolizes, or serves as a representation of another entity.
-
B.
rimRepresents
Indicates that one entity serves as a representation, model, or stand-in for another entity within a specific context or system.
-
C.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
D.
isRepresentiveOf
Indicates that one entity serves as an official agent, spokesperson, or proxy acting on behalf of another entity.
-
E.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270d7cbc819086eea86be04a2ec0 |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.