Triple
T27532574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Politics of Timor-Leste |
E695010
|
entity |
| Predicate | nationalLanguageInPolitics |
P98844
|
FINISHED |
| Object | Tetum |
—
|
NE NERFINISHED |
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: Tetum | Statement: [Politics of Timor-Leste, nationalLanguageInPolitics, Tetum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalLanguageInPolitics Context triple: [Politics of Timor-Leste, nationalLanguageInPolitics, Tetum]
-
A.
languageOfPoliticalContext
Indicates the language in which a given political context, discourse, or situation is expressed or conducted.
-
B.
languageOfCampaigning
Indicates the language used to conduct or communicate a campaign (e.g., political, marketing, or advocacy efforts).
-
C.
languageOfPoliticalWork
Indicates the language in which a political work (such as a document, speech, or publication) is expressed or written.
-
D.
nationalLanguageStatus
Indicates that a language holds official or nationally recognized status within a country or political entity.
-
E.
nationalLanguageSpoken
chosen
Indicates that a particular language is officially recognized and commonly used as a national language within a given country or region.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 1:27 p.m.