Triple
T31968359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncharted: Legacy of Thieves Collection |
E816240
|
entity |
| Predicate | regionRating |
P197956
|
FINISHED |
| Object | ESRB T |
—
|
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: ESRB T | Statement: [Uncharted: Legacy of Thieves Collection, regionRating, ESRB T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionRating Context triple: [Uncharted: Legacy of Thieves Collection, regionRating, ESRB T]
-
A.
regionStrength
Indicates the relative level of influence, power, or dominance that one region holds within a specified context or comparison.
-
B.
regionRankContext
Indicates the relative ranking or position of something within a specific geographic or regional context.
-
C.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
D.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
E.
rankingRegion
Indicates the geographic or administrative region within which a ranking or ordered comparison of entities is defined or evaluated.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_69febce420b081908e1c052751a22b1f |
completed | May 9, 2026, 4:49 a.m. |
Created at: May 1, 2026, 12:10 a.m.