Triple
T35137779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallout Tactics: Brotherhood of Steel |
E1014620
|
entity |
| Predicate | hasCampaignLocation |
P39699
|
FINISHED |
| Object | Midwestern United States |
—
|
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: Midwestern United States | Statement: [Fallout Tactics: Brotherhood of Steel, hasCampaignLocation, Midwestern United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignLocation Context triple: [Fallout Tactics: Brotherhood of Steel, hasCampaignLocation, Midwestern United States]
-
A.
locationOfCampaign
chosen
Indicates the place or geographic area where a particular campaign is conducted or based.
-
B.
hasCampaignMode
Indicates that something includes or supports a dedicated campaign mode, typically a structured, story- or mission-based sequence of play or use.
-
C.
hasTrialLocation
Indicates that a trial or legal proceeding takes place at, or is associated with, a specific location.
-
D.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:02 p.m.