Triple
T30801863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descent: Freespace – The Great War (Amiga port) |
E784389
|
entity |
| Predicate | hasCampaignStructure |
P196363
|
FINISHED |
| Object | mission-based |
—
|
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: mission-based | Statement: [Descent: Freespace – The Great War (Amiga port), hasCampaignStructure, mission-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignStructure Context triple: [Descent: Freespace – The Great War (Amiga port), hasCampaignStructure, mission-based]
-
A.
hasCampaignName
Indicates that an entity is associated with a specific campaign identified by a particular name.
-
B.
hasOrganizingCampaignType
Indicates that an entity is associated with a specific type or category of organizing campaign.
-
C.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
- F. None of above. chosen
Provenance (4 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: April 29, 2026, 8:42 p.m.