Triple

T2731686
Position Surface form Disambiguated ID Type / Status
Subject Eubalaena australis E60328 entity
Predicate feedingAreas P41703 FINISHED
Object high-latitude subantarctic waters 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: high-latitude subantarctic waters | Statement: [Eubalaena australis, feedingAreas, high-latitude subantarctic waters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: feedingAreas
Context triple: [Eubalaena australis, feedingAreas, high-latitude subantarctic waters]
  • A. foodSources
    Indicates a relationship where one entity serves as a source of food or nourishment for another entity.
  • B. feedingStructure
    Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
  • C. primaryFood
    Indicates that one entity serves as the main or most important food source for another entity.
  • D. collectingArea
    Indicates the total surface area over which something (typically a device or system) gathers or receives a substance, signal, or resource.
  • E. preysOn
    Indicates that one entity hunts, kills, and consumes another entity as a food source.
  • 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_69ab4b75cd908190b691ef0d1801acda completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdaf011548190beb9c3feee7b743f completed March 7, 2026, 7:59 a.m.
PD Predicate disambiguation batch_69abd82859348190bce3be8f2e9d60ba completed March 7, 2026, 7:47 a.m.
PDg Predicate description generation batch_69abd968b2148190929af432c9d8001f completed March 7, 2026, 7:53 a.m.
Created at: March 6, 2026, 9:56 p.m.