Triple
T29156814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagaj ‘es Itu’u |
E739070
|
entity |
| Predicate | authorityDomain |
P49097
|
FINISHED |
| Object | customary affairs |
—
|
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: customary affairs | Statement: [Gagaj ‘es Itu’u, authorityDomain, customary affairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityDomain Context triple: [Gagaj ‘es Itu’u, authorityDomain, customary affairs]
-
A.
authorityWithin
Indicates that one entity holds recognized power, control, or decision-making authority inside the scope, domain, or jurisdiction defined by another entity.
-
B.
areaOfAuthority
chosen
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
-
C.
domainGoverned
Indicates that one domain or territory is politically controlled, administered, or ruled by another authority or governing entity.
-
D.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
E.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 11:45 a.m.