Triple
T27750572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Gaming Zone |
E702102
|
entity |
| Predicate | offeredGame |
P73493
|
FINISHED |
| Object | Hearts |
—
|
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: Hearts | Statement: [Microsoft Gaming Zone, offeredGame, Hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredGame Context triple: [Microsoft Gaming Zone, offeredGame, Hearts]
-
A.
offersGame
chosen
Indicates that one entity provides or makes a game available to another entity.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
-
D.
homeGamesOf
Indicates that the subject is a home game (or set of home games) played by the specified team or entity.
-
E.
clubGamesFor
Indicates a relationship where a player participates in games on behalf of a specific club.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 4:19 p.m.