Triple
T3867931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiribati Uniting Church |
E91905
|
entity |
| Predicate | affiliationScope |
P25607
|
FINISHED |
| Object | national church |
—
|
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 church | Statement: [Kiribati Uniting Church, affiliationScope, national church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliationScope Context triple: [Kiribati Uniting Church, affiliationScope, national church]
-
A.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
B.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
-
C.
affiliationStart
Indicates the point in time when an entity’s formal association or membership with another entity begins.
-
D.
scopeType
chosen
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
senderAffiliation
Indicates that the subject is institutionally or organizationally associated with the sender of a message or communication.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3cc1a88190924125a86f72fd5b |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.