Triple
T21542234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keller family home |
E531519
|
entity |
| Predicate | hasFeatureInPlay |
P123426
|
FINISHED |
| Object | backyard setting |
—
|
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: backyard setting | Statement: [Keller family home, hasFeatureInPlay, backyard setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatureInPlay Context triple: [Keller family home, hasFeatureInPlay, backyard setting]
-
A.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
B.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
C.
hasPlayer
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
D.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
-
E.
settingWithinPlay
chosen
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
- 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_69e0c45f17148190949c330ab9c27706 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb58c34808190b0eb54ba01e2cc13 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:28 p.m.