Triple
T23187612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic skua |
E579634
|
entity |
| Predicate | breedingLatitudeZone |
P103885
|
FINISHED |
| Object | high northern latitudes |
—
|
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 northern latitudes | Statement: [Arctic skua, breedingLatitudeZone, high northern latitudes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breedingLatitudeZone Context triple: [Arctic skua, breedingLatitudeZone, high northern latitudes]
-
A.
primaryBreedingRegions
Indicates the main geographic areas where a species typically breeds or reproduces.
-
B.
biogeographicZone
chosen
Indicates the biogeographic region or ecological zone in which an entity (such as a species or habitat) naturally occurs or is distributed.
-
C.
regionOfAdaptation
Indicates the geographic or environmental region to which an entity is specifically adapted.
-
D.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
E.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd4c6f481908b6138a44b98c8a7 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.