Triple
T26708282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphecotheres |
E673337
|
entity |
| Predicate | eyeRegion |
P51923
|
FINISHED |
| Object | conspicuous bare skin around eye |
—
|
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: conspicuous bare skin around eye | Statement: [Sphecotheres, eyeRegion, conspicuous bare skin around eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeRegion Context triple: [Sphecotheres, eyeRegion, conspicuous bare skin around eye]
-
A.
eyeLocation
Indicates the spatial position or placement of an eye relative to a reference object or coordinate system.
-
B.
eyeCharacteristic
chosen
Indicates a relationship where an entity possesses a specific attribute, feature, or quality of its eyes.
-
C.
eyeType
Indicates the specific kind or category of eyes an entity has, such as their form, structure, or visual style.
-
D.
eyeFeatureObserved
Indicates that a specific characteristic or condition of the eye has been detected or recorded through observation.
-
E.
eyeAssociation
Indicates a relationship where one entity is associated with, linked to, or characterized by a particular eye or eye-related feature 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617bcfbb0819092a1334dc7553a97 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:34 a.m.