Triple
T15103061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl Mosque |
E360716
|
entity |
| Predicate | hasSanctity |
P67686
|
FINISHED |
| Object | royal private mosque |
—
|
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: royal private mosque | Statement: [Pearl Mosque, hasSanctity, royal private mosque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSanctity Context triple: [Pearl Mosque, hasSanctity, royal private mosque]
-
A.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
B.
hasHolinessType
chosen
Indicates a relationship where an entity is assigned or associated with a specific type or category of holiness.
-
C.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
D.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
E.
hasOldSanctuary
Indicates that an entity possesses or is associated with an old or former sanctuary.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00551521c8190b48d1a074bb4bdfc |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.