Triple
T11195453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Flyway |
E264909
|
entity |
| Predicate | connectsBreedingGrounds |
P2564
|
FINISHED |
| Object | northern North America |
—
|
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: northern North America | Statement: [Central Flyway, connectsBreedingGrounds, northern North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBreedingGrounds Context triple: [Central Flyway, connectsBreedingGrounds, northern North America]
-
A.
domesticationCenter
Indicates the place or region where a species was first brought under human control and selectively bred, marking the origin of its domestication.
-
B.
connectsArea
chosen
Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
-
C.
connectsLandform
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
D.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
E.
connectsIslands
Indicates a relationship where something (such as a structure, route, or link) joins or provides passage between two or more islands.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.