Triple
T18672936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caucasian grouse |
E456526
|
entity |
| Predicate | altitudinalMigration |
P52178
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Caucasian grouse, altitudinalMigration, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudinalMigration Context triple: [Caucasian grouse, altitudinalMigration, partial]
-
A.
verticalMigration
chosen
Indicates movement of an entity up and down along a vertical axis, typically in a repeated or cyclical pattern over time.
-
B.
migratoryBehavior
Indicates the pattern, timing, and routes of movement that an entity follows when migrating from one location or region to another.
-
C.
directionOfMigration
Indicates the geographic direction or path along which a migration movement proceeds from its origin toward its destination.
-
D.
altitudeEffect
Indicates how a change in altitude influences or modifies some property, condition, or outcome.
-
E.
migratoryStatus
Indicates whether an entity regularly moves between different geographic areas according to a recurring (often seasonal) migration 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b34fd881909f1b049a325d8826 |
completed | April 19, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.