Triple
T18447649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarch Grove Sanctuary |
E450697
|
entity |
| Predicate | migrationPhase |
P4275
|
FINISHED |
| Object | overwintering |
—
|
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: overwintering | Statement: [Monarch Grove Sanctuary, migrationPhase, overwintering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationPhase Context triple: [Monarch Grove Sanctuary, migrationPhase, overwintering]
-
A.
migrationTiming
Indicates the temporal characteristics or schedule of when a migration event occurs or is expected to occur.
-
B.
migrationBackground
Indicates that an entity has a personal or familial history of moving from one country or region to another, typically across national borders.
-
C.
migration
chosen
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
D.
migrationPolicy
Indicates the rules or strategies governing how entities move, transfer, or transition from one context, location, or state to another.
-
E.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52645cb88819086b0e70b6613edcd |
completed | April 19, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.