Triple
T19694224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icon series (reissue line) |
E472910
|
entity |
| Predicate | languageOfPackaging |
P48899
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Icon series (reissue line), languageOfPackaging, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfPackaging Context triple: [Icon series (reissue line), languageOfPackaging, English]
-
A.
languageOfProduct
chosen
Indicates the language in which a product is written, labeled, presented, or otherwise made available.
-
B.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
C.
languageOfMaterial
Indicates the language in which a given material, resource, or content is expressed or presented.
-
D.
brandLanguageVariant
Indicates that one language variant of a brand is related to or derived from another language version of the same brand.
-
E.
governingLanguage
Indicates the language that holds official or authoritative status over a given entity, such as a region, organization, or document.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6421385e88190b22b12ab3d851dea |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.