Triple
T28309184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .223 Remington |
E713949
|
entity |
| Predicate | popularForGameType |
P5812
|
FINISHED |
| Object | varmints |
—
|
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: varmints | Statement: [.223 Remington, popularForGameType, varmints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularForGameType Context triple: [.223 Remington, popularForGameType, varmints]
-
A.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
B.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
C.
isOftenPlayedBy
Indicates that one entity frequently performs, interprets, or executes another entity, such as a musician often playing a particular piece or instrument.
-
D.
notableGameType
chosen
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
E.
typicallyPlays
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 11:39 p.m.