Triple
T22326797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | warp-weighted loom |
E551921
|
entity |
| Predicate | warpDirection |
P117356
|
FINISHED |
| Object | warp hangs downward from upper beam |
—
|
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: warp hangs downward from upper beam | Statement: [warp-weighted loom, warpDirection, warp hangs downward from upper beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warpDirection Context triple: [warp-weighted loom, warpDirection, warp hangs downward from upper beam]
-
A.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
B.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
C.
isDirection
chosen
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
-
D.
directionalConfiguration
Indicates a specific spatial or directional arrangement that one entity has relative to another.
-
E.
transmissionDirection
Indicates the direction in which something is transmitted or passed from one entity to another.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157693460819087c165481eb9e128 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.