Triple
T38645057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsair |
E938692
|
entity |
| Predicate | isInSinglePlayerCampaign |
P43217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Corsair, isInSinglePlayerCampaign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInSinglePlayerCampaign Context triple: [Corsair, isInSinglePlayerCampaign, true]
-
A.
hasSinglePlayer
chosen
Indicates that something includes, supports, or is designed for a single-player mode or experience.
-
B.
isInMultiplayer
Indicates that an entity is currently participating in a multiplayer context or session rather than a single-player one.
-
C.
isGameSavingPlay
Indicates that a particular play or action prevents an imminent loss or major setback, effectively preserving a win or favorable outcome in a game or competition.
-
D.
isMultiplayerContentFor
Indicates that a piece of content is designed to be used or experienced in a multiplayer context for a specific game or application.
-
E.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.