Triple
T32629163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Silent Ones |
E834153
|
entity |
| Predicate | relationToGame |
P29155
|
FINISHED |
| Object | set after events of Full Throttle (approximate) |
—
|
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: set after events of Full Throttle (approximate) | Statement: [The Silent Ones, relationToGame, set after events of Full Throttle (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToGame Context triple: [The Silent Ones, relationToGame, set after events of Full Throttle (approximate)]
-
A.
relationToMainGame
Indicates how a given item, event, or component is connected or relevant to the primary or core game experience.
-
B.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
-
C.
associatedWithGame
Indicates that there is a relationship or connection between an entity and a particular game.
-
D.
relatedGame
chosen
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
-
E.
relationToLeague
Indicates the type or nature of a team's or participant's association with a specific league (e.g., membership, affiliation, or standing).
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:07 a.m.