Triple
T20453441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Player 001 |
E501712
|
entity |
| Predicate | gamePrivilege |
P19034
|
FINISHED |
| Object | exempt from being shot in Red Light, Green Light |
—
|
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: exempt from being shot in Red Light, Green Light | Statement: [Player 001, gamePrivilege, exempt from being shot in Red Light, Green Light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamePrivilege Context triple: [Player 001, gamePrivilege, exempt from being shot in Red Light, Green Light]
-
A.
holderPrivileges
chosen
Indicates that one entity possesses specific rights, permissions, or advantages granted to the holder of another entity.
-
B.
gameDelivery
Indicates that a game is being provided, distributed, or transferred from one party or source to another.
-
C.
gameOwnershipModel
Indicates the type of ownership relationship users have with a game, such as whether they fully own, license, or temporarily access it.
-
D.
sharesGameClientWith
Indicates that two entities use or are associated with the same game client software or instance.
-
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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d039af08190827bf765b50515a8 |
completed | April 20, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.