Triple
T29911337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCNAction |
E759680
|
entity |
| Predicate | canBeReversed |
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: [SCNAction, canBeReversed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeReversed Context triple: [SCNAction, canBeReversed, true]
-
A.
mayReverse
chosen
Indicates that an action, process, or state can be undone or returned to a previous condition.
-
B.
isUsedToReverse
Indicates that one entity serves the function of undoing, inverting, or changing the direction or effect of another entity or process.
-
C.
canRevertTo
Indicates that one state, version, or condition has the ability to be changed back or restored to another prior state, version, or condition.
-
D.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
E.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 29, 2026, 6:10 p.m.