Triple
T28245621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petromyzontiformes |
E712156
|
entity |
| Predicate | eyeDevelopment |
P164150
|
FINISHED |
| Object | larvae with poorly developed eyes |
—
|
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: larvae with poorly developed eyes | Statement: [Petromyzontiformes, eyeDevelopment, larvae with poorly developed eyes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeDevelopment Context triple: [Petromyzontiformes, eyeDevelopment, larvae with poorly developed eyes]
-
A.
eyeCount
Indicates the number of eyes an entity has.
-
B.
eyeLocation
Indicates the spatial position or placement of an eye relative to a reference object or coordinate system.
-
C.
eyeCondition
Indicates that an entity has, experiences, or is characterized by a particular condition or disorder affecting the eyes.
-
D.
eyeMigration
Indicates the movement or displacement of an eye (or eyes) from one position to another within an organism’s body or visual system.
-
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. chosen
Provenance (4 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c84f1c8190879e643c18e74e75 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 11:01 p.m.