Triple
T31558117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protacanthopterygii |
E805182
|
entity |
| Predicate | containsAnadromousSpecies |
P83094
|
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: [Protacanthopterygii, containsAnadromousSpecies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAnadromousSpecies Context triple: [Protacanthopterygii, containsAnadromousSpecies, true]
-
A.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
containsAquaticMembers
chosen
Indicates that a group or collection includes one or more members that live in or are adapted to aquatic environments.
-
C.
anadromous
Indicates that an aquatic organism migrates from the sea into freshwater to spawn.
-
D.
hasAquaticEcosystem
Indicates that an entity possesses, contains, or is associated with an ecosystem primarily based in water (such as rivers, lakes, wetlands, or oceans).
-
E.
nativeFish
Indicates that the fish species is originally from, and naturally occurs in, the specified geographic area or ecosystem.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: April 30, 2026, 10:13 p.m.