Triple
T16585965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mousetrap (play-within-a-play) |
E402956
|
entity |
| Predicate | settingWithinPlay |
P123426
|
FINISHED |
| Object | the Danish court |
—
|
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: the Danish court | Statement: [The Mousetrap (play-within-a-play), settingWithinPlay, the Danish court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingWithinPlay Context triple: [The Mousetrap (play-within-a-play), settingWithinPlay, the Danish court]
-
A.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
usesPlayingArea
Indicates that one entity makes use of a particular playing area as the space in which an activity or event takes place.
-
C.
playableSide
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
-
D.
decidingPlay
Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
-
E.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599cbc448190bc80eef4ad58eb41 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:16 a.m.