Triple
T12900361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emacs state |
E308595
|
entity |
| Predicate | switchableFrom |
P67036
|
FINISHED |
| Object | Normal state |
—
|
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: Normal state | Statement: [Emacs state, switchableFrom, Normal state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: switchableFrom Context triple: [Emacs state, switchableFrom, Normal state]
-
A.
switchOnBy
Indicates that an entity is turned on or activated as the result of an action performed by another entity.
-
B.
changedFrom
chosen
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
adaptsFrom
Indicates that one entity is derived, modified, or transformed from another, preserving core elements while changing form, medium, or context.
-
D.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
E.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.