Triple
T18784348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wingless |
E459334
|
entity |
| Predicate | hasConservedRoleIn |
P133006
|
FINISHED |
| Object | metazoan development |
—
|
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: metazoan development | Statement: [wingless, hasConservedRoleIn, metazoan development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConservedRoleIn Context triple: [wingless, hasConservedRoleIn, metazoan development]
-
A.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
hasHistoricalRoleAs
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
C.
hasCompanionRoleIn
Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
-
D.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
E.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977ffa648190be5f682bba47fb0a |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.