Triple
T8460619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Andean deer |
E200028
|
entity |
| Predicate | rangeFragmentation |
P58854
|
FINISHED |
| Object | highly fragmented distribution |
—
|
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: highly fragmented distribution | Statement: [South Andean deer, rangeFragmentation, highly fragmented distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeFragmentation Context triple: [South Andean deer, rangeFragmentation, highly fragmented distribution]
-
A.
fragmentationLevel
chosen
Indicates the degree to which something is broken into smaller, separate parts or segments.
-
B.
successorStateFragmentation
Indicates that a successor state experiences division or breakup into multiple smaller political or administrative units.
-
C.
numberOfFragmentsApprox
Indicates an approximate count of how many fragments or pieces are associated with the subject.
-
D.
rangeSize
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
-
E.
rangeState
Indicates that an entity’s state or condition falls within a specified range or interval.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49fca788190a8728ff74f4d26f5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.