Triple
T26502465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawk Hill |
E669456
|
entity |
| Predicate | raptorMigrationSeason |
P60503
|
FINISHED |
| Object | fall |
—
|
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: fall | Statement: [Hawk Hill, raptorMigrationSeason, fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raptorMigrationSeason Context triple: [Hawk Hill, raptorMigrationSeason, fall]
-
A.
migratoryBirdsFrom
Indicates a relationship where the subject is a location or region that serves as the origin from which migratory birds travel or disperse.
-
B.
migratoryBehavior
Indicates the pattern, timing, and routes of movement that an entity follows when migrating from one location or region to another.
-
C.
migratoryStatus
Indicates whether an entity regularly moves between different geographic areas according to a recurring (often seasonal) migration pattern.
-
D.
hasSeasonalMigration
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
-
E.
hasSeasonalSpecies
chosen
Indicates that certain species are present or occur only during specific seasons in relation to a given context or location.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6135b47248190a67aa93a1e6b936c |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:14 a.m.