Triple
T1630162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific lamprey |
E35237
|
entity |
| Predicate | hasOralDiscFunction |
P30393
|
FINISHED |
| Object | attaches to host fish |
—
|
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: attaches to host fish | Statement: [Pacific lamprey, hasOralDiscFunction, attaches to host fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOralDiscFunction Context triple: [Pacific lamprey, hasOralDiscFunction, attaches to host fish]
-
A.
mouthState
Indicates the current condition or configuration of an entity’s mouth, such as whether it is open, closed, or in another specific state.
-
B.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
C.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
D.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
E.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a94319becc819089c2daf45fe08a0c |
completed | March 5, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:28 p.m.