Triple
T1741647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruminantia |
E38245
|
entity |
| Predicate | hasAnatomicalFeature |
P31173
|
FINISHED |
| Object | complex stomach with multiple chambers |
—
|
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: complex stomach with multiple chambers | Statement: [Ruminantia, hasAnatomicalFeature, complex stomach with multiple chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnatomicalFeature Context triple: [Ruminantia, hasAnatomicalFeature, complex stomach with multiple chambers]
-
A.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
B.
hasLimbs
Indicates that an entity possesses one or more limbs as physical appendages.
-
C.
embryologicalFeature
Indicates a relationship where one entity is an anatomical or biological structure characterized or defined by its origin, development, or properties during the embryonic stage.
-
D.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
E.
hasAntennae
Indicates that one entity possesses or is equipped with antennae as a physical feature.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab3c2559ac8190905186406fcaccb9 |
completed | March 6, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69aa61c4023c819099cbe439aefda71f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.