Triple
T36504954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miotapirus |
E899434
|
entity |
| Predicate | hasBodyPlanSimilarTo |
P94757
|
FINISHED |
| Object | modern tapirs |
—
|
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: modern tapirs | Statement: [Miotapirus, hasBodyPlanSimilarTo, modern tapirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyPlanSimilarTo Context triple: [Miotapirus, hasBodyPlanSimilarTo, modern tapirs]
-
A.
hasBodyPlanType
Indicates that an organism possesses a particular overall structural or morphological body plan type.
-
B.
hasBodyPlanFeature
Indicates that an organism’s body plan includes a specific structural or morphological feature.
-
C.
hasSimilarityTo
chosen
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
D.
hasMovementStructureAnalogousTo
Indicates that one entity’s movement structure is similar or functionally analogous to that of another entity.
-
E.
floorPlanSimilarTo
Indicates that one entity has a floor plan that is similar in layout or structure to that 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:10 p.m.