Triple
T31579248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teke carpets |
E805777
|
entity |
| Predicate | borderDesign |
P198060
|
FINISHED |
| Object | multiple narrow borders |
—
|
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: multiple narrow borders | Statement: [Teke carpets, borderDesign, multiple narrow borders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDesign Context triple: [Teke carpets, borderDesign, multiple narrow borders]
-
A.
bordersDesigner
Indicates that one entity serves as a bordering or edge-defining designer for another entity, establishing a design relationship focused on boundaries or borders.
-
B.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
C.
borderText
Indicates that one entity is the textual content displayed along the border of another entity.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
frontDesign
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
- F. None of above. chosen
Provenance (4 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
| PDg | Predicate description generation | batch_69fec5c3f8248190b835a8e4eba470c4 |
completed | May 9, 2026, 5:27 a.m. |
Created at: April 30, 2026, 10:22 p.m.