Triple
T26502467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawk Hill |
E669456
|
entity |
| Predicate | raptorMigrationPeakMonths |
P108895
|
FINISHED |
| Object | October |
—
|
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: October | Statement: [Hawk Hill, raptorMigrationPeakMonths, October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raptorMigrationPeakMonths Context triple: [Hawk Hill, raptorMigrationPeakMonths, October]
-
A.
typicalPeakDateRange
Indicates the usual calendar period during which the referenced phenomenon or activity most commonly reaches its highest intensity or occurrence.
-
B.
peakSeasonMonth
chosen
Indicates the month or months during which something (such as demand, activity, or occurrence) reaches its highest or most intense level.
-
C.
timeOfMigration
Indicates the specific time or period during which a migration event occurs.
-
D.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
E.
hasSeasonalMigration
Indicates that an entity regularly moves between different locations according to seasonal or cyclical environmental changes.
- 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_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:14 a.m.