Triple
T5601331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurukun |
E147125
|
entity |
| Predicate | hasReligiousFacilities |
P1191
|
FINISHED |
| Object | Christian churches |
—
|
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: Christian churches | Statement: [Aurukun, hasReligiousFacilities, Christian churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousFacilities Context triple: [Aurukun, hasReligiousFacilities, Christian churches]
-
A.
hasReligiousSite
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
hasPlaceOfWorship
chosen
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
D.
hasClericalStructure
Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
-
E.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020da519c81908626b243e40db263 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.