Triple
T31083849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPC-E |
E792173
|
entity |
| Predicate | humanReadableTextPlacement |
P108446
|
FINISHED |
| Object | below the bars |
—
|
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: below the bars | Statement: [UPC-E, humanReadableTextPlacement, below the bars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanReadableTextPlacement Context triple: [UPC-E, humanReadableTextPlacement, below the bars]
-
A.
humanReadable
Indicates that something is expressed in a form that is easily understandable or interpretable by humans.
-
B.
readingPlacement
Indicates a relationship where an entity is assigned or located at a specific position or level based on its reading or reading-related criteria.
-
C.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
D.
textAlignment
Indicates how text is positioned or aligned relative to a reference frame, such as margins, columns, or other layout boundaries.
-
E.
textLocation
chosen
Indicates the spatial or positional relationship of a piece of text within a larger document, page, or layout.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695fb5f60819099ac1f20472cfc61 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.