Triple
T312155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Masjid an-Nabawi |
E7629
|
entity |
| Predicate | flooring |
P5519
|
FINISHED |
| Object | marble and other stone materials |
—
|
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: marble and other stone materials | Statement: [Al-Masjid an-Nabawi, flooring, marble and other stone materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flooring Context triple: [Al-Masjid an-Nabawi, flooring, marble and other stone materials]
-
A.
floor
Indicates that one entity is located on or forms the walking surface (the floor) beneath another entity within a space.
-
B.
hasFloor
chosen
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
C.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
D.
floorPlan
Indicates that one entity serves as the architectural layout or room arrangement blueprint for another entity (such as a building or space).
-
E.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4aa16881909b2c8404b85992df |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.