Triple
T30819295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Rukn al-Shami |
E784871
|
entity |
| Predicate | isStructuralElementOf |
P69124
|
FINISHED |
| Object | Kaaba building |
—
|
NE NERFINISHED |
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: Kaaba building | Statement: [al-Rukn al-Shami, isStructuralElementOf, Kaaba building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStructuralElementOf Context triple: [al-Rukn al-Shami, isStructuralElementOf, Kaaba building]
-
A.
isAComponentOf
chosen
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
B.
isWithinStructure
Indicates that one entity is located inside the physical or logical boundaries of another structure.
-
C.
isStructureGroupOf
Indicates that one entity functions as the structural grouping or organizing framework that encompasses or defines the structure of another entity.
-
D.
isFeatureOf
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
E.
containsStructuralUnit
Indicates that one entity includes or encompasses another entity as a structural subunit or component within its overall structure.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6906b8f048190b3051f9ece75bd3a |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:44 p.m.