Triple
T21148965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VV |
E521133
|
entity |
| Predicate | perforationPullDown |
P135041
|
FINISHED |
| Object | 8-perf horizontal |
—
|
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: 8-perf horizontal | Statement: [VV, perforationPullDown, 8-perf horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perforationPullDown Context triple: [VV, perforationPullDown, 8-perf horizontal]
-
A.
perforation
chosen
Indicates the creation or presence of a hole or series of holes made through an object or material, typically by piercing or boring.
-
B.
downSpecial
Indicates that an entity performs or is associated with a special action or ability triggered by a downward input or downward-directed command.
-
C.
negativePerforationPitch
Indicates that one entity has a perforation spacing or pitch value that is oriented or measured in a negative direction relative to a defined reference.
-
D.
dropDirection
Indicates the direction in which an object is or should be dropped or allowed to fall.
-
E.
verticalDrop_m
Indicates the vertical distance, measured in meters, through which something drops or falls from a higher point to a lower point.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723ffb578819080a000987459a8a5 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.