Triple
T5840480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking textiles |
E129579
|
entity |
| Predicate | weaveStructure |
P65164
|
FINISHED |
| Object | tabby weave |
—
|
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: tabby weave | Statement: [Viking textiles, weaveStructure, tabby weave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaveStructure Context triple: [Viking textiles, weaveStructure, tabby weave]
-
A.
hasWeave
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular weave or woven pattern associated with another entity.
-
B.
weavingCenter
Indicates that an entity serves as a central place or hub where weaving activities are carried out or coordinated.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
producesStructure
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
-
E.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.