Triple
T35855220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titanfall |
E1036482
|
entity |
| Predicate | hasCampaignStyle |
P200152
|
FINISHED |
| Object | multiplayer campaign |
—
|
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: multiplayer campaign | Statement: [Titanfall, hasCampaignStyle, multiplayer campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignStyle Context triple: [Titanfall, hasCampaignStyle, multiplayer campaign]
-
A.
hasCampaignMode
chosen
Indicates that something includes or supports a dedicated campaign mode, typically a structured, story- or mission-based sequence of play or use.
-
B.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to another entity.
-
C.
hasCampaignStructure
Indicates that one entity possesses, defines, or is associated with a particular organizational or strategic campaign framework of another entity.
-
D.
hasBroadcastStyle
Indicates that one entity is characterized by, or associated with, a particular manner or style of broadcasting.
-
E.
hasCampaignName
Indicates that an entity is associated with a specific campaign identified by a particular name.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:06 p.m.