Triple
T2692674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucky Strike |
E58439
|
entity |
| Predicate | laterProductType |
P41091
|
FINISHED |
| Object | cigarettes |
—
|
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: cigarettes | Statement: [Lucky Strike, laterProductType, cigarettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterProductType Context triple: [Lucky Strike, laterProductType, cigarettes]
-
A.
laterProducedBy
Indicates that something is produced or created by an entity at a later time than some referenced or implied production event.
-
B.
laterPlatform
Indicates that one entity occurs, appears, or is positioned on a platform that comes after another platform in time or sequence.
-
C.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
D.
notableProductType
Indicates that an entity is particularly well-known or distinguished for producing or offering a specific type of product.
-
E.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0dd97c81909a60cf200f57c087 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd879bb808190bd2c34de1664c816 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.