Triple
T2007438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAN-13 barcode system |
E43616
|
entity |
| Predicate | symbolStructure |
P13707
|
FINISHED |
| Object | left guard pattern |
—
|
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: left guard pattern | Statement: [EAN-13 barcode system, symbolStructure, left guard pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolStructure Context triple: [EAN-13 barcode system, symbolStructure, left guard pattern]
-
A.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
B.
symbolType
chosen
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
C.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
D.
symbolDescription
Indicates that a symbol is associated with or defined by a particular descriptive explanation or meaning.
-
E.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8999e108190a07daa01452a5dab |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.