Triple
T28080596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green |
E709663
|
entity |
| Predicate | isPerceivedBy |
P4830
|
FINISHED |
| Object | human eye cones sensitive to medium wavelengths |
—
|
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: human eye cones sensitive to medium wavelengths | Statement: [Green, isPerceivedBy, human eye cones sensitive to medium wavelengths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerceivedBy Context triple: [Green, isPerceivedBy, human eye cones sensitive to medium wavelengths]
-
A.
hasPerception
chosen
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
B.
isSeeOf
Indicates that one entity serves as the episcopal or ecclesiastical seat (see) of another, typically a bishop or similar religious office.
-
C.
hasFanPerception
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
-
D.
hasSight
Indicates that one entity possesses the ability or capacity to see or visually perceive.
-
E.
perceptionBySelf
Indicates that an entity has a perception, awareness, or sensory experience of itself.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:51 p.m.