Triple
T11529865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfenstein: Youngblood |
E273389
|
entity |
| Predicate | cooperativePlay |
P99554
|
FINISHED |
| Object | supports online co-op |
—
|
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: supports online co-op | Statement: [Wolfenstein: Youngblood, cooperativePlay, supports online co-op]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cooperativePlay Context triple: [Wolfenstein: Youngblood, cooperativePlay, supports online co-op]
-
A.
cooperateThrough
Indicates that entities work together or coordinate their actions by means of a specific intermediary, method, or channel.
-
B.
hasCooperative
Indicates that one entity participates in a cooperative relationship or partnership with another entity.
-
C.
isCooperative
Indicates that an entity engages willingly and constructively in joint actions or relationships with others, working together toward shared goals.
-
D.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
E.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839878948190b170e64629d6f2db |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.