Triple
T10417710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R91 |
E245562
|
entity |
| Predicate | recoverySystem |
P94036
|
FINISHED |
| Object | arrested recovery |
—
|
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: arrested recovery | Statement: [R91, recoverySystem, arrested recovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoverySystem Context triple: [R91, recoverySystem, arrested recovery]
-
A.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
B.
recoveryMethod
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
C.
recoveryConfiguration
Indicates a configuration relationship specifying how an entity should be restored, recovered, or brought back to an operational state after failure or disruption.
-
D.
recoveryPlan
Indicates a planned set of actions or strategies designed to restore a system, entity, or situation from a degraded, failed, or disrupted state back to an acceptable or normal condition.
-
E.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
- F. None of above. chosen
Provenance (4 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea1194e08190a18c3b3002147493 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:11 p.m.