Triple
T5792212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian carpet |
E128421
|
entity |
| Predicate | hasKnotType |
P65863
|
FINISHED |
| Object | asymmetrical Persian knot |
—
|
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: asymmetrical Persian knot | Statement: [Persian carpet, hasKnotType, asymmetrical Persian knot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKnotType Context triple: [Persian carpet, hasKnotType, asymmetrical Persian knot]
-
A.
hasNodeType
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
-
B.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
-
C.
hasJointType
Indicates that one entity is associated with, or characterized by, a specific type or category of joint.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5870b88190bbfaac2782635128 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c024861bc88190a17782c1982fbb3e |
completed | March 22, 2026, 5:19 p.m. |
Created at: March 22, 2026, 3:51 p.m.