Triple
T18012681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branchiopoda |
E430920
|
entity |
| Predicate | bodyAppendages |
P50709
|
FINISHED |
| Object | leaf-like thoracic appendages |
—
|
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: leaf-like thoracic appendages | Statement: [Branchiopoda, bodyAppendages, leaf-like thoracic appendages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyAppendages Context triple: [Branchiopoda, bodyAppendages, leaf-like thoracic appendages]
-
A.
appendages
chosen
Indicates that one entity has limbs or projecting body parts that are attached to another entity.
-
B.
isProminentPartOf
Indicates that something forms a major, highly noticeable, or significant component of a larger whole.
-
C.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
D.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
E.
hasMechanicalAppendages
Indicates that an entity possesses one or more appendages that are mechanical or artificially constructed rather than purely biological.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b520ea088190b74903f1e1ba49e2 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.