Triple
T38643683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warfronts |
E938664
|
entity |
| Predicate | supportsCooperativePlayers |
P197343
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [Warfronts, supportsCooperativePlayers, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCooperativePlayers Context triple: [Warfronts, supportsCooperativePlayers, 20]
-
A.
hasMultiplayerCoop
chosen
Indicates that an entity (such as a game or application) supports a multiplayer mode where multiple users can cooperate or play together simultaneously.
-
B.
supportsCooperative
Indicates that one entity provides assistance, resources, or endorsement to enable or strengthen another entity’s cooperative activities or partnerships.
-
C.
cooperativePlay
Indicates that two or more entities are engaging in a shared, mutually coordinated activity or game toward a common goal.
-
D.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
-
E.
isCooperative
Indicates that an entity engages willingly and constructively in joint actions or relationships with others, working together toward shared goals.
- 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.