Triple
T6777029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resígaro language |
E155582
|
entity |
| Predicate | speakerNumber |
P72731
|
FINISHED |
| Object | very few speakers remaining |
—
|
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: very few speakers remaining | Statement: [Resígaro language, speakerNumber, very few speakers remaining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speakerNumber Context triple: [Resígaro language, speakerNumber, very few speakers remaining]
-
A.
speakerType
Indicates the role or category of a participant in a communicative act (e.g., narrator, quoted speaker, system voice) within a given context.
-
B.
speakerConfiguration
Indicates how speakers are arranged or assigned within an audio or communication setup.
-
C.
speakerMP
Indicates that the subject is a Member of Parliament who holds or is identified with the role of Speaker (or a speaker-related parliamentary position).
-
D.
identifiesSpeakerAs
Indicates that one entity designates or recognizes another entity as the speaker of a given utterance or communication.
-
E.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
- F. None of above. chosen
Provenance (4 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26725208190b64935cfd08b2aff |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d182213c819086fcbbfd3d64d80b |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:13 p.m.