Triple
T11731126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NJOY |
E278897
|
entity |
| Predicate | hasMarketingRestrictions |
P101041
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NJOY, hasMarketingRestrictions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketingRestrictions Context triple: [NJOY, hasMarketingRestrictions, yes]
-
A.
mayHaveRestriction
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
B.
hasAwardRestriction
Indicates that there is a limitation, condition, or constraint placed on receiving or granting an award.
-
C.
hasMarketingIcon
Indicates that an entity is associated with, or represented by, a specific marketing-related icon or symbol.
-
D.
hasLanguageRestriction
Indicates that an entity is subject to limitations or specific conditions regarding the languages it can use, support, or be associated with.
-
E.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d94de08190a7184cf26d8cb94e |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.