Triple
T7575732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strigiformes |
E179357
|
entity |
| Predicate | canRotateHead |
P23580
|
FINISHED |
| Object | up to about 270 degrees |
—
|
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: up to about 270 degrees | Statement: [Strigiformes, canRotateHead, up to about 270 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRotateHead Context triple: [Strigiformes, canRotateHead, up to about 270 degrees]
-
A.
headRetraction
Indicates a relationship where an entity pulls or draws its head back from a previous position.
-
B.
tiltingCapability
chosen
Indicates the ability of one entity to tilt or be tilted relative to another or to a reference orientation.
-
C.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
D.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
E.
rotatesWith
Indicates that two or more entities turn or spin together in a coordinated or mechanically linked manner, typically sharing the same rotational motion or axis.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94a25148190b5b76e000e0336c4 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.