Triple
T29100913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total War |
E736636
|
entity |
| Predicate | hasBoardGameAdaptation |
P183996
|
FINISHED |
| Object | Total War: ROME The Board Game |
—
|
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: Total War: ROME The Board Game | Statement: [Total War, hasBoardGameAdaptation, Total War: ROME The Board Game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoardGameAdaptation Context triple: [Total War, hasBoardGameAdaptation, Total War: ROME The Board Game]
-
A.
hasBoardGameplay
Indicates that an entity involves or features gameplay that takes place on or around a game board.
-
B.
boardGameGeekCategory
Indicates that something is classified under a specific category in the BoardGameGeek taxonomy of board game types or themes.
-
C.
adaptedAsPlayBy
Indicates that a work has been transformed or reinterpreted into a play by a particular adapter.
-
D.
hasGraphicNovelAdaptation
Indicates that a work has been adapted into a graphic novel format.
-
E.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: April 28, 2026, 11:12 a.m.