Triple
T31607413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook Islands Christian Church |
E806528
|
entity |
| Predicate | mainIslandOfActivity |
P110177
|
FINISHED |
| Object | Rarotonga |
—
|
NE NERFINISHED |
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: Rarotonga | Statement: [Cook Islands Christian Church, mainIslandOfActivity, Rarotonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainIslandOfActivity Context triple: [Cook Islands Christian Church, mainIslandOfActivity, Rarotonga]
-
A.
primaryIslandOfOperation
chosen
Indicates that an entity mainly conducts its activities or operations on a specified island.
-
B.
isMainIsland
Indicates that an island is the primary or most significant island within a group, region, or country.
-
C.
mainIslandNetwork
Indicates that an entity belongs to or is part of the primary or central island network within a larger geographic or infrastructural system.
-
D.
majorActivity
Indicates that the related entity performs, participates in, or is primarily associated with a main or most significant activity.
-
E.
centralIsland
Indicates that one entity is an island located at or near the central region of another geographic or spatial context.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:35 p.m.