Triple
T31810586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprinus |
E811992
|
entity |
| Predicate | hasCirri |
P123246
|
FINISHED |
| Object | barbels near mouth |
—
|
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: barbels near mouth | Statement: [Cyprinus, hasCirri, barbels near mouth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCirri Context triple: [Cyprinus, hasCirri, barbels near mouth]
-
A.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
B.
hasCircle
Indicates that one entity possesses, contains, or includes a circle as part of its structure or composition.
-
C.
hasCiliation
chosen
Indicates that an entity possesses cilia or is characterized by the presence of ciliation.
-
D.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
E.
hasHCR
Indicates that an entity possesses, is associated with, or is governed by a specific Health Care Regulation (HCR).
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 30, 2026, 11:43 p.m.