Triple
T15999380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtua Tennis |
E388055
|
entity |
| Predicate | gameplayPace |
P73974
|
FINISHED |
| Object | fast |
—
|
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: fast | Statement: [Virtua Tennis, gameplayPace, fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayPace Context triple: [Virtua Tennis, gameplayPace, fast]
-
A.
combatPace
Indicates the speed, intensity, or tempo at which combat or a battle is being conducted between opposing forces.
-
B.
isFastPaced
chosen
Indicates that an activity, event, or process proceeds quickly with rapid progression and little downtime.
-
C.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
D.
gameplayImpact
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
E.
spinRate
Indicates the rotational speed at which an object or system is spinning, typically measured as revolutions per unit time.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142dc081c819082527e3fa8773460 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:55 a.m.