Triple
T26233906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Asian–Australasian Flyway migratory birds |
E656112
|
entity |
| Predicate | nonBreedingRegion |
P151286
|
FINISHED |
| Object | Australia |
—
|
NE NERFINISHED |
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: Australia | Statement: [East Asian–Australasian Flyway migratory birds, nonBreedingRegion, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonBreedingRegion Context triple: [East Asian–Australasian Flyway migratory birds, nonBreedingRegion, Australia]
-
A.
nonBreedingRangeIncludes
chosen
Indicates that the specified geographic area is part of the region where the species occurs outside its breeding season.
-
B.
primaryBreedingRegions
Indicates the main geographic areas where a species typically breeds or reproduces.
-
C.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
D.
nearNaturalRegion
Indicates that one entity is located close to a specified natural region or area in geographic space.
-
E.
notUsedInRegion
Indicates that something is not utilized, applied, or present within a specified geographic or administrative region.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d88c7b0819096aa999f8f366dbd |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9 p.m.