Triple
T9216602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little River (Tennessee) |
E221255
|
entity |
| Predicate | hasFishType |
P45992
|
FINISHED |
| Object | trout |
—
|
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: trout | Statement: [Little River (Tennessee), hasFishType, trout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishType Context triple: [Little River (Tennessee), hasFishType, trout]
-
A.
hasFishingSpecies
chosen
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
B.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
C.
hasAquariumType
Indicates that an entity is associated with, or classified by, a specific type or category of aquarium.
-
D.
containsAquariumFish
Indicates that one entity includes or holds aquarium fish within it.
-
E.
requiresFishType
Indicates that something must specify or depend on a particular type or category of fish in order to be valid or complete.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda096358819096d4e790da057512 |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.