Triple
T22691672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bull Durham tobacco |
E561065
|
entity |
| Predicate | becamePopularInPeriod |
P105129
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Bull Durham tobacco, becamePopularInPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becamePopularInPeriod Context triple: [Bull Durham tobacco, becamePopularInPeriod, late 19th century]
-
A.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
-
B.
decadeOfPopularization
Indicates the decade during which something became widely known, used, or popular.
-
C.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
D.
popularizedAfter
Indicates that one entity became widely known, accepted, or influential only after another specified entity had already gained popularity.
-
E.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789adcc48190b4a717166d5dba19 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.