Triple
T33422859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Respawn Entertainment |
E855888
|
entity |
| Predicate | hasOnlineGame |
P34364
|
FINISHED |
| Object | Apex Legends |
—
|
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: Apex Legends | Statement: [Respawn Entertainment, hasOnlineGame, Apex Legends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineGame Context triple: [Respawn Entertainment, hasOnlineGame, Apex Legends]
-
A.
hasOnlineGameConcept
Indicates that an entity is associated with, involves, or is characterized by a particular concept related to online games.
-
B.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
C.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
D.
hasOnlineLobby
Indicates that an entity provides or supports an online lobby feature where users can gather, interact, or prepare before engaging in the main activity or service.
-
E.
hasOnlineActivity
chosen
Indicates that an entity engages in or possesses some form of activity or presence on the internet or digital platforms.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.