Triple
T24212365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scratch-N-Sniff |
E600585
|
entity |
| Predicate | typicalLocationOnProduct |
P155223
|
FINISHED |
| Object | designated printed areas |
—
|
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: designated printed areas | Statement: [Scratch-N-Sniff, typicalLocationOnProduct, designated printed areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationOnProduct Context triple: [Scratch-N-Sniff, typicalLocationOnProduct, designated printed areas]
-
A.
locatedOnFront
Indicates that one entity is positioned on the front side or face of another entity.
-
B.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
C.
typicalControlLocation
Indicates the usual or standard physical location from which control or operation of something is exercised.
-
D.
расположенаНа
Indicates that one entity is located on the surface or area of another entity.
-
E.
insigniaLocation
Indicates the physical position or placement of an insignia on or relative to an entity.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820401bc81909ae1837b41c85526 |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:55 p.m.