Triple
T15238749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Averostra |
E364196
|
entity |
| Predicate | commonMorphology |
P31789
|
FINISHED |
| Object | hollow limb bones in many members |
—
|
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: hollow limb bones in many members | Statement: [Averostra, commonMorphology, hollow limb bones in many members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMorphology Context triple: [Averostra, commonMorphology, hollow limb bones in many members]
-
A.
notableMorphology
Indicates that an entity is characterized by a distinctive or noteworthy physical form, structure, or shape.
-
B.
morphologicalClass
Indicates the classification of an entity based on its morphological form or structural pattern.
-
C.
morphologicalComplexity
Indicates the degree to which a language’s word forms are structurally intricate, involving multiple morphemes, inflections, or derivational processes.
-
D.
relatedMorphologicalFeature
chosen
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
E.
typicalWordFormation
Indicates the usual or most common way in which a word is formed from other linguistic elements (such as roots, affixes, or compounds).
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007da7e988190925a9b67b8070bc7 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.