Triple
T9326042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAN-2 |
E224386
|
entity |
| Predicate | isNotUsedFor |
P7974
|
FINISHED |
| Object | primary product identification |
—
|
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: primary product identification | Statement: [EAN-2, isNotUsedFor, primary product identification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotUsedFor Context triple: [EAN-2, isNotUsedFor, primary product identification]
-
A.
notAutomaticallyUsedBy
Indicates that something is not used by another entity in an automatic or default manner and instead requires explicit action or configuration to be used.
-
B.
notTypicallyUsedFor
chosen
Indicates that something is generally not used for a particular purpose, function, or activity under normal circumstances.
-
C.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
D.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
E.
notUsedOnModel
Indicates that a particular item, component, or feature is not applied, installed, or utilized on the specified model.
- 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_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. |
Created at: March 30, 2026, 7:39 p.m.