Triple
T26707189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceanodroma |
E673312
|
entity |
| Predicate | activityZone |
P165361
|
FINISHED |
| Object | mostly far from land outside breeding season |
—
|
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: mostly far from land outside breeding season | Statement: [Oceanodroma, activityZone, mostly far from land outside breeding season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activityZone Context triple: [Oceanodroma, activityZone, mostly far from land outside breeding season]
-
A.
activityDomain
Indicates the general field, sector, or area of activity within which an entity operates or performs its main actions.
-
B.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
C.
possiblePlaceOfActivity
Indicates that a location is a plausible or candidate site where the referenced entity may carry out or have carried out an activity.
-
D.
arenaType
Indicates the specific kind or category of arena associated with an entity or event.
-
E.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 3:34 a.m.