Triple
T35421578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Switch Palace |
E1023808
|
entity |
| Predicate | replayable |
P108689
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Green Switch Palace, replayable, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replayable Context triple: [Green Switch Palace, replayable, no]
-
A.
playable
Indicates that an entity can be used or performed as a game, media, or activity in its intended interactive or functional form.
-
B.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
C.
isReplay
Indicates that an event, action, or content instance is a repeated playback or reproduction of a previously occurring original.
-
D.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
E.
hasReplay
chosen
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:03 p.m.