Triple
T36955726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viva Piñata series |
E914182
|
entity |
| Predicate | typicalESRBRating |
P82154
|
FINISHED |
| Object | E for Everyone |
E367838
|
NE 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: E for Everyone | Statement: [Viva Piñata series, typicalESRBRating, E for Everyone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalESRBRating Context triple: [Viva Piñata series, typicalESRBRating, E for Everyone]
-
A.
ESRBrating
chosen
Indicates the official content rating assigned to a game or media product by the ESRB, reflecting its suitability for different age groups.
-
B.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalDifficulty
Indicates the usual or characteristic level of difficulty associated with performing an action or achieving a particular outcome.
-
E.
typicalPower
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
- F. None of above.
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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c3a73788190ab9079adfc537786 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.