Triple
T17768467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branta hutchinsii |
E443570
|
entity |
| Predicate | wasFormerlyConsidered |
P120323
|
FINISHED |
| Object | subspecies of Branta canadensis |
—
|
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: subspecies of Branta canadensis | Statement: [Branta hutchinsii, wasFormerlyConsidered, subspecies of Branta canadensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFormerlyConsidered Context triple: [Branta hutchinsii, wasFormerlyConsidered, subspecies of Branta canadensis]
-
A.
wasFormerlyClassifiedAs
chosen
Indicates that an entity previously belonged to a particular class or category but no longer does so.
-
B.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
C.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
D.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
E.
wasOriginally
Indicates that an entity had a particular state, form, type, or affiliation at an earlier time, which has since changed.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fd8aa081909c8ee9264af15c69 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.