Triple
T19052559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dek Island |
E466296
|
entity |
| Predicate | hasReligionSiteType |
P34373
|
FINISHED |
| Object | monastery island |
—
|
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: monastery island | Statement: [Dek Island, hasReligionSiteType, monastery island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionSiteType Context triple: [Dek Island, hasReligionSiteType, monastery island]
-
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.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
D.
religiousSiteType
chosen
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
E.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc03dfa08190924a1b8073364fa1 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.