Triple
T35439059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enga language |
E1024290
|
entity |
| Predicate | usedInLocalAdministration |
P184896
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Enga language, usedInLocalAdministration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLocalAdministration Context triple: [Enga language, usedInLocalAdministration, true]
-
A.
hasLocalAdministrativeSignificance
Indicates that something holds official importance or authority within a specific local administrative area or jurisdiction.
-
B.
usedForAdministrativePurposes
Indicates that something is employed in managing, organizing, or overseeing official, institutional, or organizational activities and records.
-
C.
usedInDistrict
Indicates that something is utilized, applied, or implemented within the boundaries or jurisdiction of a specific district.
-
D.
localUse
chosen
Indicates that something is used, applied, or consumed within a specific local area, context, or jurisdiction rather than more broadly or globally.
-
E.
usedAdministrativeSystemOf
Indicates that one entity made use of another entity’s administrative system to perform or manage its administrative functions.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:04 p.m.