Triple
T34770201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleutian tern |
E1002341
|
entity |
| Predicate | migratesToRegion |
P83648
|
FINISHED |
| Object | tropical Pacific Ocean |
—
|
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: tropical Pacific Ocean | Statement: [Aleutian tern, migratesToRegion, tropical Pacific Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migratesToRegion Context triple: [Aleutian tern, migratesToRegion, tropical Pacific Ocean]
-
A.
transferredRegion
Indicates that control, ownership, or responsibility for a geographic or administrative region has been moved from one entity to another.
-
B.
regionOfMigration
Indicates the geographic area from which an entity or population moves or migrates.
-
C.
hasDestinationRegion
chosen
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
D.
migratedAcross
Indicates movement of an entity from one side of a boundary, region, or area to the other, typically implying a significant relocation or crossing.
-
E.
migratesBetween
Indicates movement of an entity from one location or region to another, typically in a recurring or seasonal pattern.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.