Triple
T15172311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport Box |
E362516
|
entity |
| Predicate | hasUsageMethod |
P33646
|
FINISHED |
| Object | lit with flame and inhaled through filter |
—
|
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: lit with flame and inhaled through filter | Statement: [Newport Box, hasUsageMethod, lit with flame and inhaled through filter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageMethod Context triple: [Newport Box, hasUsageMethod, lit with flame and inhaled through filter]
-
A.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
B.
usesMethods
chosen
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
C.
hasUsageNote
Indicates that there is an associated explanatory note describing how or when something should be used.
-
D.
hasUseCase
Indicates that one entity is employed, applied, or utilized as a solution or method to address a particular need, problem, or scenario associated with another entity.
-
E.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006501b488190a2ab09dbf1532571 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.