Triple
T20760963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energon blades |
E510973
|
entity |
| Predicate | canRetract |
P139986
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Energon blades, canRetract, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRetract Context triple: [Energon blades, canRetract, true]
-
A.
canRevertTo
Indicates that one state, version, or condition has the ability to be changed back or restored to another prior state, version, or condition.
-
B.
canRepeal
Indicates that one entity has the authority or power to revoke, annul, or cancel a rule, decision, or action established by another entity.
-
C.
canReinstate
Indicates that one entity has the authority or ability to restore another entity or state to a previous valid or active condition.
-
D.
canRetain
Indicates that one entity has the ability or permission to keep, hold, or maintain possession or control of another entity over time.
-
E.
mayReverse
chosen
Indicates that an action, process, or state can be undone or returned to a previous condition.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c248701081908ae49fca933e05f6 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.