Triple
T8562494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totally Games |
E202721
|
entity |
| Predicate | gameFeatures |
P92849
|
FINISHED |
| Object | mission briefings |
—
|
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: mission briefings | Statement: [Totally Games, gameFeatures, mission briefings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameFeatures Context triple: [Totally Games, gameFeatures, mission briefings]
-
A.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
B.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
C.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
D.
performanceFeature
Indicates that an entity possesses a characteristic, capability, or attribute specifically related to its performance or operational effectiveness.
-
E.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe94c0c3c8190aca981c07b090dc0 |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69d4c7c15c708190997122e3e472734f |
completed | April 7, 2026, 9 a.m. |
Created at: March 30, 2026, 6:20 p.m.