Triple
T35133541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beothuk language |
E1014505
|
entity |
| Predicate | lastSpeakers |
P56181
|
FINISHED |
| Object | died in 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: died in 19th century | Statement: [Beothuk language, lastSpeakers, died in 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastSpeakers Context triple: [Beothuk language, lastSpeakers, died in 19th century]
-
A.
lastSpeakersAssociatedWith
Indicates a relationship where certain entities are identified as the most recent or final speakers associated with another entity, such as an event, session, or conversation.
-
B.
lastKnownSpeakers
chosen
Indicates the people or entities most recently known to use or speak a particular language.
-
C.
lastKnownSpeakersDate
Indicates the date on which the last known speakers of a language or dialect were recorded or documented.
-
D.
lastSpeakersLocatedIn
Indicates that the most recent speakers in a given context are situated or based in a specified location.
-
E.
lastKnownSpeaker
Indicates the entity that was most recently identified or recorded as speaking in a given context or interaction.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c6c9bac819083af967f6f403ca7 |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.