Triple
T26676220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidency of Timor-Leste |
E672461
|
entity |
| Predicate | hasCeremonialFunctions |
P168925
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Presidency of Timor-Leste, hasCeremonialFunctions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeremonialFunctions Context triple: [Presidency of Timor-Leste, hasCeremonialFunctions, yes]
-
A.
ceremonialFunctionsInclude
Indicates that a set of ceremonial functions encompasses or contains a particular ceremonial function as one of its components.
-
B.
ceremonialRoleInvolves
Indicates that a ceremonial role includes or entails performing a particular action, duty, or function as part of that ceremony.
-
C.
hasCeremonies
Indicates that an entity conducts, includes, or is associated with one or more formal ceremonies or ritual events.
-
D.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
E.
ceremonialFeatures
Indicates that something possesses attributes, elements, or characteristics specifically associated with ceremonies or ritual practices.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 3:16 a.m.