Triple
T9325948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAN-8 barcode system |
E224384
|
entity |
| Predicate | usesBarAndSpaceWidths |
P87529
|
FINISHED |
| Object | four-module width patterns |
—
|
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: four-module width patterns | Statement: [EAN-8 barcode system, usesBarAndSpaceWidths, four-module width patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBarAndSpaceWidths Context triple: [EAN-8 barcode system, usesBarAndSpaceWidths, four-module width patterns]
-
A.
hasBars
Indicates that one entity possesses, contains, or is equipped with bars as a defining feature or component.
-
B.
hasUpperBarLength
Indicates that an entity possesses an upper bar whose length is specified or constrained by the related value or object.
-
C.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
D.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
E.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f88e988190bb896a3d7c3c723c |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:39 p.m.