Triple
T15888989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaenoptera acutorostrata |
E385265
|
entity |
| Predicate | feedingArea |
P82322
|
FINISHED |
| Object | higher latitude productive 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: higher latitude productive waters | Statement: [Balaenoptera acutorostrata, feedingArea, higher latitude productive waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedingArea Context triple: [Balaenoptera acutorostrata, feedingArea, higher latitude productive waters]
-
A.
feedingAreas
Indicates areas or locations where one entity provides food or nourishment to another.
-
B.
feedingHabitat
chosen
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
C.
foragingZone
Indicates the area or region where an entity typically searches for and collects food.
-
D.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
-
E.
foragingTendency
Indicates the degree to which an entity is inclined or likely to engage in searching for and gathering food or resources.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.