Triple
T21466265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eucestoda |
E529600
|
entity |
| Predicate | attachmentStructure |
P93025
|
FINISHED |
| Object | suckers on scolex |
—
|
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: suckers on scolex | Statement: [Eucestoda, attachmentStructure, suckers on scolex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attachmentStructure Context triple: [Eucestoda, attachmentStructure, suckers on scolex]
-
A.
attachmentType
chosen
Indicates the specific kind or category of attachment that relates one entity to another.
-
B.
annexStructure
Indicates that one structure is attached or added to another as an annex or extension.
-
C.
associatesStructure
Indicates a relationship where one entity is linked or connected to a particular structure, typically to denote that the structure is relevant, attached, or functionally associated with it.
-
D.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
E.
lapStructure
Indicates that one entity forms a lap-like structural surface or support upon which another entity can rest or be positioned.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f32b5c8190bfa5acb3c9b1ab3b |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:11 p.m.