Triple
T14490760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrine of the Cloak of the Prophet Muhammad |
E359354
|
entity |
| Predicate | accessToRelic |
P62129
|
FINISHED |
| Object | cloak is rarely displayed to the public |
—
|
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: cloak is rarely displayed to the public | Statement: [Shrine of the Cloak of the Prophet Muhammad, accessToRelic, cloak is rarely displayed to the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToRelic Context triple: [Shrine of the Cloak of the Prophet Muhammad, accessToRelic, cloak is rarely displayed to the public]
-
A.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
B.
relicBroughtBy
Indicates that a relic was transported or delivered to a location or context by a specific agent or entity.
-
C.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
D.
hasRelicsStatus
chosen
Indicates that an entity holds a particular status or condition specifically related to relics.
-
E.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.