Triple
T1145437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derringer pistol |
E23553
|
entity |
| Predicate | wasPopularIn |
P911
|
FINISHED |
| Object | 19th century United States |
—
|
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: 19th century United States | Statement: [Derringer pistol, wasPopularIn, 19th century United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPopularIn Context triple: [Derringer pistol, wasPopularIn, 19th century United States]
-
A.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
B.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified time period.
-
C.
popularInCentury
chosen
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
D.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
E.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc51244c8190bcd533f3e80c8f17 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.