Triple
T18052871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pallas's sandgrouse |
E431961
|
entity |
| Predicate | rangeExpansionEvent |
P35360
|
FINISHED |
| Object | 19th-century irruption into western Europe |
—
|
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: 19th-century irruption into western Europe | Statement: [Pallas's sandgrouse, rangeExpansionEvent, 19th-century irruption into western Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeExpansionEvent Context triple: [Pallas's sandgrouse, rangeExpansionEvent, 19th-century irruption into western Europe]
-
A.
rangeExpansion
chosen
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
B.
rangeExtenderOption
Indicates that an entity offers or is associated with an optional feature or configuration that extends its operational range.
-
C.
rangeState
Indicates that an entity’s state or condition falls within a specified range or interval.
-
D.
rangeBehavior
Indicates how an entity behaves or operates when interacting with or within a specified range or distance.
-
E.
rangeUnitExtensibility
Indicates that the range unit can be extended or customized beyond its default or predefined limits.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c0ff580c8190bc3ca04025476255 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.