Triple
T4804583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaction Motors XLR99 |
E106917
|
entity |
| Predicate | restartable |
P21085
|
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: [Reaction Motors XLR99, restartable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartable Context triple: [Reaction Motors XLR99, restartable, true]
-
A.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
B.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
C.
restartCapability
chosen
Indicates the ability or permission for an entity to be restarted, typically after a stop, failure, or configuration change.
-
D.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
-
E.
reopenedFor
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.