Triple
T1584506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aves |
E34033
|
entity |
| Predicate | hasJawStructure |
P31173
|
FINISHED |
| Object | toothless beak in modern species |
—
|
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: toothless beak in modern species | Statement: [Aves, hasJawStructure, toothless beak in modern species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJawStructure Context triple: [Aves, hasJawStructure, toothless beak in modern species]
-
A.
hasTeeth
Indicates that one entity possesses teeth as a physical feature.
-
B.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
C.
hasOralDiscFunction
Indicates that an entity possesses a specific functional role or capability associated with its oral disc.
-
D.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
E.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of another entity.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.