Triple
T34668441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleginopsidae |
E890314
|
entity |
| Predicate | exampleFisherySpecies |
P45992
|
FINISHED |
| Object | Eleginops maclovinus |
—
|
NE NERFINISHED |
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: Eleginops maclovinus | Statement: [Eleginopsidae, exampleFisherySpecies, Eleginops maclovinus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleFisherySpecies Context triple: [Eleginopsidae, exampleFisherySpecies, Eleginops maclovinus]
-
A.
gameFish
Indicates a relationship where an animal is considered a fish that is commonly pursued or valued in recreational or sport fishing.
-
B.
fisheryType
Indicates the specific category or kind of fishery associated with an entity, such as its operational or regulatory classification.
-
C.
nativeFish
Indicates that the fish species is originally from, and naturally occurs in, the specified geographic area or ecosystem.
-
D.
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.
-
E.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f904b0819091ffa4ea4621e8b4 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.