Triple
T12766402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puquina |
E305135
|
entity |
| Predicate | hasApproximateExtinctionCentury |
P7427
|
FINISHED |
| Object | 19th century |
—
|
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 | Statement: [Puquina, hasApproximateExtinctionCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateExtinctionCentury Context triple: [Puquina, hasApproximateExtinctionCentury, 19th century]
-
A.
extinctionPeriod
chosen
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
B.
extinctionDate
Indicates the date or time at which an entity (typically a species or lineage) ceased to exist.
-
C.
possiblyExtinctBy
Indicates that an entity is believed or suspected to have gone extinct as a result of the specified cause or agent.
-
D.
wasOnceNearExtinction
Indicates that the entity’s population or existence was at one time so low or threatened that it was in serious danger of disappearing entirely.
-
E.
hasExtinctMembers
Indicates that at least some members of the referenced group, class, or category are no longer living or existing.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df1ef148190af525532fcb0933b |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.