Triple
T33623885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synanceia horrida |
E861344
|
entity |
| Predicate | hasEyesPosition |
P115176
|
FINISHED |
| Object | dorsal surface of head |
—
|
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: dorsal surface of head | Statement: [Synanceia horrida, hasEyesPosition, dorsal surface of head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEyesPosition Context triple: [Synanceia horrida, hasEyesPosition, dorsal surface of head]
-
A.
hasEyes
Indicates that an entity possesses eyes as physical features.
-
B.
hasInclinationToLineOfSight
Indicates that one entity is oriented or directed in such a way that it tends toward having a line of sight to another entity or location.
-
C.
eyeLocation
chosen
Indicates the spatial position or placement of an eye relative to a reference object or coordinate system.
-
D.
hasHeadPosition
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
-
E.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f81ea9388190bf58dad0672e7697 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.