Triple
T19987532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NES-101 |
E493971
|
entity |
| Predicate | resetButton |
P127735
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NES-101, resetButton, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resetButton Context triple: [NES-101, resetButton, yes]
-
A.
resetType
Indicates the specific kind or method of reset applied to an entity, process, or system state.
-
B.
hasResetButton
chosen
Indicates that an entity is equipped with a reset button that can restore it to a default or initial state.
-
C.
resetRule
Indicates that a rule is returned to its initial or default state, typically clearing any prior changes or accumulated effects.
-
D.
rebootOf
Indicates that one work is a new version that restarts or reimagines the story, continuity, or franchise of another earlier work.
-
E.
memoryResets
Indicates that an entity’s memory is cleared, reverted, or restarted, removing or resetting previously stored information.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fdd1a5c8190af756632aac38bf4 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.