Triple
T5516377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cestoda |
E144692
|
entity |
| Predicate | requiresIntermediateHost |
P51723
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cestoda, requiresIntermediateHost, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresIntermediateHost Context triple: [Cestoda, requiresIntermediateHost, true]
-
A.
intermediateHost
chosen
Indicates that one entity serves as a temporary carrier or conduit through which something (such as a pathogen, resource, or signal) passes on its way between an origin and a final target.
-
B.
hostRequirement
Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
-
C.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
D.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
E.
alternatingHost
Indicates a relationship where two or more entities take turns serving as host in a recurring or cyclical manner.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5e8ce08190b7f5f2131bebcd4f |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.