Triple
T27021313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Connecticut Lake |
E680669
|
entity |
| Predicate | hasNearbyFishSpecies |
P188073
|
FINISHED |
| Object | brook 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: brook trout | Statement: [Second Connecticut Lake, hasNearbyFishSpecies, brook trout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFishSpecies Context triple: [Second Connecticut Lake, hasNearbyFishSpecies, brook trout]
-
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.
containsFish
Indicates that one entity holds, includes, or has fish within its boundaries or contents.
-
C.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
D.
nativeFish
Indicates that the fish species is originally from, and naturally occurs in, the specified geographic area or ecosystem.
-
E.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fba28684208190921694f23e350c3b |
completed | May 6, 2026, 8:20 p.m. |
Created at: April 27, 2026, 7:08 a.m.