Triple
T16441672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirurida |
E399315
|
entity |
| Predicate | hasDevelopmentStage |
P113179
|
FINISHED |
| Object | larval stage in intermediate host |
—
|
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: larval stage in intermediate host | Statement: [Spirurida, hasDevelopmentStage, larval stage in intermediate host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevelopmentStage Context triple: [Spirurida, hasDevelopmentStage, larval stage in intermediate host]
-
A.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
B.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
C.
hasDevelopmentSystem
Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
-
D.
hasDevelopmentDimension
Indicates that something possesses or is associated with a particular aspect or dimension of development.
-
E.
hasFormationStage
chosen
Indicates that an entity is associated with a particular stage or phase in its formation or development process.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba91dc48190bc35db60f63d36d3 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.