Triple
T8913661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chlorophanes spiza |
E212243
|
entity |
| Predicate | migrationStatus |
P35309
|
FINISHED |
| Object | mostly resident |
—
|
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: mostly resident | Statement: [Chlorophanes spiza, migrationStatus, mostly resident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationStatus Context triple: [Chlorophanes spiza, migrationStatus, mostly resident]
-
A.
typicalMigrationStatus
chosen
Indicates the usual or characteristic migration state or pattern associated with an entity.
-
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
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
D.
migrationEnded
Indicates that a previously ongoing migration process or movement from one place or state to another has come to an end.
-
E.
migrationEvent
Indicates an event in which one or more entities move or relocate from one place or context to another, typically across defined boundaries or regions.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65276b788190ab76372d0d871fef |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.