Triple
T10511591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Church of Melanesia |
E247926
|
entity |
| Predicate | hasMissionPriority |
P25698
|
FINISHED |
| Object | rural communities |
—
|
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: rural communities | Statement: [Anglican Church of Melanesia, hasMissionPriority, rural communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMissionPriority Context triple: [Anglican Church of Melanesia, hasMissionPriority, rural communities]
-
A.
missionPriority
chosen
Indicates the relative level of importance or urgency assigned to a mission compared to other missions or tasks.
-
B.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
-
C.
hasPredecessorMission
Indicates that a mission occurs after and is directly preceded by another specific mission in a sequence.
-
D.
hasPriorityAt
Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
-
E.
hasMissionActivity
Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b5fcb8819087a23a2b26aecd70 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:27 p.m.