Triple
T8025357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strigidae |
E186839
|
entity |
| Predicate | headMobility |
P80641
|
FINISHED |
| Object | highly flexible neck |
—
|
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: highly flexible neck | Statement: [Strigidae, headMobility, highly flexible neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headMobility Context triple: [Strigidae, headMobility, highly flexible neck]
-
A.
headRetraction
Indicates a relationship where an entity pulls or draws its head back from a previous position.
-
B.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
C.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
D.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
E.
headShape
Indicates the characteristic form or contour of an entity’s head.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ec9983c8190b468c13f5b5beb63 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.