Triple
T30505505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenakel language |
E776257
|
entity |
| Predicate | hasReligionDomain |
P202445
|
FINISHED |
| Object | used in Christian church services on Tanna |
—
|
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: used in Christian church services on Tanna | Statement: [Lenakel language, hasReligionDomain, used in Christian church services on Tanna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionDomain Context triple: [Lenakel language, hasReligionDomain, used in Christian church services on Tanna]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
D.
recognizesReligion
Indicates that one entity formally acknowledges or accepts another entity as a valid or legitimate religion.
-
E.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
- F. None of above. chosen
Provenance (4 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
| PDg | Predicate description generation | batch_6a00809836f081908de40255d4f4d525 |
completed | May 10, 2026, 12:56 p.m. |
Created at: April 29, 2026, 8:15 p.m.