Triple
T33422862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Respawn Entertainment |
E855888
|
entity |
| Predicate | hasSinglePlayerGame |
P43217
|
FINISHED |
| Object | Star Wars Jedi: Fallen Order |
—
|
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: Star Wars Jedi: Fallen Order | Statement: [Respawn Entertainment, hasSinglePlayerGame, Star Wars Jedi: Fallen Order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSinglePlayerGame Context triple: [Respawn Entertainment, hasSinglePlayerGame, Star Wars Jedi: Fallen Order]
-
A.
hasSinglePlayer
chosen
Indicates that something includes, supports, or is designed for a single-player mode or experience.
-
B.
hasStandaloneGame
Indicates that an entity has its own independently released, self-contained game associated with it.
-
C.
hasMultiplayer
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
D.
isSingleEliminationGame
Indicates that the game is part of a single-elimination format where a loss results in immediate elimination from the competition.
-
E.
notPlayableInMultiplayer
Indicates that the referenced content or action cannot be used or accessed in multiplayer mode.
- 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_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:36 a.m.