Triple
T10289784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foundation Stone |
E241330
|
entity |
| Predicate | visibleInside |
P9694
|
FINISHED |
| Object | Dome of the Rock interior |
—
|
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: Dome of the Rock interior | Statement: [Foundation Stone, visibleInside, Dome of the Rock interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleInside Context triple: [Foundation Stone, visibleInside, Dome of the Rock interior]
-
A.
visibleAt
chosen
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
B.
visibleRemains
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
C.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
D.
visibleByDefault
Indicates that something is initially shown or accessible without requiring any additional action or configuration to make it visible.
-
E.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of another entity.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:41 a.m.