Triple
T37462550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clutchmother Zavas |
E930953
|
entity |
| Predicate | canAppearInMode |
P69305
|
FINISHED |
| Object | Arena |
—
|
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: Arena | Statement: [Clutchmother Zavas, canAppearInMode, Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAppearInMode Context triple: [Clutchmother Zavas, canAppearInMode, Arena]
-
A.
availableInMode
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
B.
appearsInGameMode
chosen
Indicates that an entity is present, available, or featured within a specified game mode.
-
C.
mayIncludeMode
Indicates that one entity is allowed to contain or support a particular mode as one of its possible configurations or options.
-
D.
hasModeCategory
Indicates that something is associated with or classified under a particular mode category (e.g., type or manner of operation or behavior).
-
E.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.