Triple
T2638399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Australian Bight |
E62802
|
entity |
| Predicate | majorMarineSpecies |
P12485
|
FINISHED |
| Object | southern right whale |
—
|
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: southern right whale | Statement: [Great Australian Bight, majorMarineSpecies, southern right whale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorMarineSpecies Context triple: [Great Australian Bight, majorMarineSpecies, southern right whale]
-
A.
hasMarineSpecies
chosen
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
B.
marineLifeTrend
Indicates a change over time in the abundance, health, or distribution of marine life populations.
-
C.
MysticetiCommonName
Indicates that a given common (vernacular) name refers to or is used for a baleen whale belonging to the suborder Mysticeti.
-
D.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
E.
hasMarineEcoregion
Indicates that an entity is associated with, or located within, a specific marine ecoregion.
- 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_69ab4c3f2dcc819082df80f5e032f690 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abd8e470ac8190bd0d6de6805afcd0 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.