Triple
T23944683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotch Tape |
E602881
|
entity |
| Predicate | hasWidthRange |
P154444
|
FINISHED |
| Object | narrow widths |
—
|
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: narrow widths | Statement: [Scotch Tape, hasWidthRange, narrow widths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWidthRange Context triple: [Scotch Tape, hasWidthRange, narrow widths]
-
A.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
B.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
hasNarrowestWidth
Indicates that one entity has the smallest width dimension compared to a specified set of entities or alternatives.
-
E.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02d07b08190acbcbb646cd9a58e |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:11 p.m.