Triple
T11731387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyft nicotine pouches |
E278903
|
entity |
| Predicate | isDiscreet |
P101049
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lyft nicotine pouches, isDiscreet, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDiscreet Context triple: [Lyft nicotine pouches, isDiscreet, true]
-
A.
isDiscretionary
Indicates that the action or decision is optional and left to personal or organizational judgment rather than being mandatory or automatic.
-
B.
isSmall
Indicates that one entity has a size that is relatively small, either in absolute terms or compared to a reference standard or another entity.
-
C.
canBeDissectedBy
Indicates that one entity is capable of being divided or analyzed into parts by another entity or method.
-
D.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
E.
isTight
Indicates that one entity fits closely or securely around, against, or within another without looseness or extra space.
- 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.