Triple
T11118714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ningaloo Niño marine heatwave events |
E262961
|
entity |
| Predicate | affectsSpeciesGroup |
P2895
|
FINISHED |
| Object | corals |
—
|
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: corals | Statement: [Ningaloo Niño marine heatwave events, affectsSpeciesGroup, corals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsSpeciesGroup Context triple: [Ningaloo Niño marine heatwave events, affectsSpeciesGroup, corals]
-
A.
affectsTaxon
chosen
Indicates that one entity has an impact or influence on a particular taxon or group of organisms.
-
B.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
C.
supportsSpeciesGroup
Indicates that one entity provides suitable conditions or resources that enable the survival or persistence of a particular group of species.
-
D.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
E.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af6fe448190b042c2e77b855b05 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.