Triple
T37530164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Haverchuck |
E933014
|
entity |
| Predicate | likesGame |
P138103
|
FINISHED |
| Object | Dungeons & Dragons |
—
|
NE NERFINISHED |
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: Dungeons & Dragons | Statement: [Bill Haverchuck, likesGame, Dungeons & Dragons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likesGame Context triple: [Bill Haverchuck, likesGame, Dungeons & Dragons]
-
A.
isOftenPlayedBy
Indicates that one entity frequently performs, interprets, or executes another entity, such as a musician often playing a particular piece or instrument.
-
B.
usesGameAs
Indicates that one entity employs or relies on a particular game as a tool, medium, or component to achieve some purpose or function.
-
C.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
D.
typicallyPlays
chosen
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
-
E.
isOftenPlayedFor
Indicates that one entity is frequently performed, used, or presented for the benefit, enjoyment, or experience of another entity.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.