Triple
T33422860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Respawn Entertainment |
E855888
|
entity |
| Predicate | hasMultiplayerGame |
P43216
|
FINISHED |
| Object | Titanfall |
—
|
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: Titanfall | Statement: [Respawn Entertainment, hasMultiplayerGame, Titanfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplayerGame Context triple: [Respawn Entertainment, hasMultiplayerGame, Titanfall]
-
A.
hasMultiplayer
chosen
Indicates that an entity (such as a game or application) supports a mode where multiple users can participate or interact simultaneously.
-
B.
isInMultiplayer
Indicates that an entity is currently participating in a multiplayer context or session rather than a single-player one.
-
C.
multiplayerCompatibleWith
Indicates that two or more entities can function together in a shared multiplayer context without conflict or incompatibility.
-
D.
supportsLocalMultiplayer
Indicates that the subject provides functionality for multiple players to play together on the same device or local network.
-
E.
supportsOnlineMultiplayer
Indicates that the subject provides functionality for multiple users to play together over an online network.
- 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_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 1:36 a.m.