Triple
T5559631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monogenea |
E145732
|
entity |
| Predicate | hasIntermediateHost |
P51723
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Monogenea, hasIntermediateHost, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntermediateHost Context triple: [Monogenea, hasIntermediateHost, no]
-
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.
hasIntermediateCity
Indicates that there is a city located between two other places along a route or connection.
-
C.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
D.
hasIntermediateStation
Indicates that a route, journey, or connection includes a station that lies between its starting point and its final destination.
-
E.
hasFormerHost
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020167afc8190b0c518907cd0d99b |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.