Triple
T35386948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-Switch |
E1022814
|
entity |
| Predicate | resetCondition |
P29156
|
FINISHED |
| Object | effect ends when timer runs out |
—
|
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: effect ends when timer runs out | Statement: [P-Switch, resetCondition, effect ends when timer runs out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resetCondition Context triple: [P-Switch, resetCondition, effect ends when timer runs out]
-
A.
terminationCondition
chosen
Indicates the condition or set of conditions under which an ongoing process, activity, or relationship is brought to an end.
-
B.
remainderCondition
Indicates that a specified remainder-based condition (such as a modulo constraint) holds between one or more values.
-
C.
releaseCondition
Indicates the circumstances or requirements under which something is allowed to be released or made available.
-
D.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
E.
returnCondition
Indicates the terms, state, or circumstances under which something that was previously given, lent, or transferred is expected or required to be returned.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.