Triple
T35415156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plecoptera |
E1023619
|
entity |
| Predicate | hasOrderCodeInBiomonitoring |
P198051
|
FINISHED |
| Object | Pleco |
—
|
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: Pleco | Statement: [Plecoptera, hasOrderCodeInBiomonitoring, Pleco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderCodeInBiomonitoring Context triple: [Plecoptera, hasOrderCodeInBiomonitoring, Pleco]
-
A.
hasBreedingCode
Indicates that an entity is associated with a specific code representing its breeding status, behavior, or category.
-
B.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
C.
hasIneCode
Indicates that an entity is associated with a specific INE (national statistics or education) code that identifies it in an official registry.
-
D.
hasKeyLaboratory
Indicates that an entity possesses or is associated with a designated key laboratory, typically as an important research or development facility under its responsibility.
-
E.
hasEvidenceCode
Indicates that a relationship, assertion, or annotation is supported or qualified by a specific type of evidence, identified by an evidence code.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
| PDg | Predicate description generation | batch_69fec4cee6a081908139ea6aa608f729 |
completed | May 9, 2026, 5:23 a.m. |
Created at: May 3, 2026, 4:03 p.m.