Triple
T23391205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Seas off the West Coast of Scotland |
E594021
|
entity |
| Predicate | hasTypicalSpecies |
P38050
|
FINISHED |
| Object | harbour porpoise |
—
|
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: harbour porpoise | Statement: [Inner Seas off the West Coast of Scotland, hasTypicalSpecies, harbour porpoise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSpecies Context triple: [Inner Seas off the West Coast of Scotland, hasTypicalSpecies, harbour porpoise]
-
A.
hasCommonSpecies
Indicates that two entities share at least one species in common.
-
B.
typicalTargetSpecies
Indicates the species that is most commonly or characteristically targeted or affected by a given action, process, or agent.
-
C.
hasLargeSpecies
Indicates that an entity possesses or includes at least one species that is considered large in size.
-
D.
hasDominantSpecies
chosen
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
E.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49bdfec8190afa592c66660c279 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.