Triple
T23129796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehabilitation and Physical Therapy Services |
E577135
|
entity |
| Predicate | targetsOutcome |
P94027
|
FINISHED |
| Object | Improved strength |
—
|
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: Improved strength | Statement: [Rehabilitation and Physical Therapy Services, targetsOutcome, Improved strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsOutcome Context triple: [Rehabilitation and Physical Therapy Services, targetsOutcome, Improved strength]
-
A.
targetOutcomeForDrivers
Indicates the specific result or objective that an action, policy, or system is intended to achieve for drivers.
-
B.
targetOutcomeForClients
chosen
Indicates the specific result or benefit that an action, service, or process is intended to achieve for clients.
-
C.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
E.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8671f48190887e57d5723e49c1 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.