Triple
T21556764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauritius kestrel |
E531911
|
entity |
| Predicate | wasOnceConsidered |
P23508
|
FINISHED |
| Object | world’s rarest bird |
—
|
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: world’s rarest bird | Statement: [Mauritius kestrel, wasOnceConsidered, world’s rarest bird]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasOnceConsidered Context triple: [Mauritius kestrel, wasOnceConsidered, world’s rarest bird]
-
A.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
B.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
C.
nowConsidered
Indicates that something has come to be regarded or classified in a particular way at the present time, possibly differing from how it was regarded before.
-
D.
usedToBe
chosen
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
E.
couldConsider
Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e04b048190ac3a9913094b4625 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.