Triple
T30253700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lut Desert |
E769276
|
entity |
| Predicate | mainReligionInSurroundingRegion |
P134933
|
FINISHED |
| Object | Islam |
E1333
|
NE 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: Islam | Statement: [Lut Desert, mainReligionInSurroundingRegion, Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainReligionInSurroundingRegion Context triple: [Lut Desert, mainReligionInSurroundingRegion, Islam]
-
A.
religionInRegion
chosen
Indicates that a particular religion is practiced or present within a specified geographic region.
-
B.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
-
C.
localReligion
Indicates that a particular religion is practiced or holds significance within a specific local area or community.
-
D.
laterReligionRegionOf
Indicates that a region became associated with a particular religion at a later time than another referenced region or context.
-
E.
religionInCountry
Indicates that a particular religion is practiced, present, or recognized within a specified country.
- F. None of above.
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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6807e374881909a0c7edfde2e8f35 |
completed | May 2, 2026, 10:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27643d4b8c81908cae65b88f089b37 |
completed | June 9, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:40 p.m.