Triple
T37457571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tempo Rogue |
E930836
|
entity |
| Predicate | playerTypeAppeal |
P194732
|
FINISHED |
| Object | players who like fast games |
—
|
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: players who like fast games | Statement: [Tempo Rogue, playerTypeAppeal, players who like fast games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerTypeAppeal Context triple: [Tempo Rogue, playerTypeAppeal, players who like fast games]
-
A.
playerAppeal
Indicates a formal request or challenge made by a player, typically seeking a review or reversal of a decision or outcome.
-
B.
levelOfAppeal
Indicates the degree or intensity to which something is attractive, interesting, or desirable to someone or something.
-
C.
typeOfAppeals
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
D.
allegedAppearanceType
Indicates the type or nature of an appearance that is claimed or reported to have occurred, without confirming that the appearance actually took place.
-
E.
spectatorAppeal
Indicates that an action, event, or entity is appealing, entertaining, or attractive to spectators or an audience.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
| PDg | Predicate description generation | batch_69fd82ebe1c081908455fc45b6e45178 |
completed | May 8, 2026, 6:30 a.m. |
Created at: May 3, 2026, 4:17 p.m.