Triple
T18602777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enteropneusta |
E454657
|
entity |
| Predicate | hasTrunkFunction |
P132751
|
FINISHED |
| Object | contains gut and gonads |
—
|
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: contains gut and gonads | Statement: [Enteropneusta, hasTrunkFunction, contains gut and gonads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrunkFunction Context triple: [Enteropneusta, hasTrunkFunction, contains gut and gonads]
-
A.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
-
B.
hasTailFunction
Indicates that one entity serves as the tail or ending functional component of another entity in a structured relationship or sequence.
-
C.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
-
D.
isOnTrunkLine
Indicates that something is located on, or directly connected to, a primary or main trunk line within a network or system.
-
E.
hasTransportFunction
Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
- F. None of above. chosen
Provenance (4 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54751d7ec81909efc4867f649002e |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.