Triple
T26039514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mambai |
E647646
|
entity |
| Predicate | statusInConstitution |
P70272
|
FINISHED |
| Object | national language of East Timor |
—
|
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: national language of East Timor | Statement: [Mambai, statusInConstitution, national language of East Timor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInConstitution Context triple: [Mambai, statusInConstitution, national language of East Timor]
-
A.
constitutionStatus
chosen
Indicates the legal or formal status of an entity as defined or recognized by a constitution.
-
B.
isPartOfConstitution
Indicates that something forms a component or section within a constitution or constitutional document.
-
C.
recognizedInConstitution
Indicates that an entity’s status, rights, or role is formally acknowledged and defined within a constitution.
-
D.
subjectToConstitution
Indicates that an entity is governed, constrained, or regulated by the rules and principles of a specific constitution.
-
E.
usesConstitution
Indicates that one entity applies, relies on, or operates according to a particular constitution as its guiding legal or organizational framework.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 9:08 a.m.