Triple
T34116897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Walking Dead: No Man’s Land |
E874996
|
entity |
| Predicate | playerAction |
P82156
|
FINISHED |
| Object | manage survivors |
—
|
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: manage survivors | Statement: [The Walking Dead: No Man’s Land, playerAction, manage survivors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerAction Context triple: [The Walking Dead: No Man’s Land, playerAction, manage survivors]
-
A.
physicalAction
Indicates a relationship where one entity performs or undergoes a tangible, bodily movement or interaction in the physical world.
-
B.
actionSpace
Indicates the set of all possible actions an agent can take in a given environment or decision-making context.
-
C.
allowsPlayerAction
chosen
Indicates that one entity permits or enables a player to perform a specific action within a system or context.
-
D.
playsShoots
Indicates that an entity participates in a sport or game using a particular shooting style or handedness (e.g., a hockey player who shoots left or right).
-
E.
announcesPlayerActions
Indicates that an entity publicly communicates or reports the actions taken by a player.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 1:53 a.m.