Triple
T341085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaaba |
E6838
|
entity |
| Predicate | materialOfCovering |
P618
|
FINISHED |
| Object | black silk and gold-embroidered cloth |
—
|
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: black silk and gold-embroidered cloth | Statement: [Kaaba, materialOfCovering, black silk and gold-embroidered cloth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialOfCovering Context triple: [Kaaba, materialOfCovering, black silk and gold-embroidered cloth]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
C.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
D.
mantlingLined
Indicates that the inner surface of a heraldic mantling is lined with a specified material, color, or pattern.
-
E.
hasOutfieldWallCovering
Indicates that an outfield wall is covered or surfaced with a particular material or type of covering.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae611f88190955fbebe2b01835b |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95197fc8190820e8ebd0d7d27fa |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.