Triple
T9056643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last to Die |
E217015
|
entity |
| Predicate | hasGameZone |
P6793
|
FINISHED |
| Object | library |
—
|
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: library | Statement: [Last to Die, hasGameZone, library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameZone Context triple: [Last to Die, hasGameZone, library]
-
A.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
B.
hasPlayAreaType
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
C.
hasShortGameArea
Indicates that an entity includes or is associated with a designated short-game practice area (e.g., for chipping, pitching, or putting).
-
D.
hasZone
chosen
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
hasPvPArea
Indicates that a location or zone is designated for player-versus-player (PvP) interactions or combat.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a75d8e881909414d745ec054182 |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee6d83c819095d8ed0779aa8511 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.