Triple
T38246308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LASIK |
E1013898
|
entity |
| Predicate | recoveryTime |
P98408
|
FINISHED |
| Object | rapid visual 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: rapid visual recovery | Statement: [LASIK, recoveryTime, rapid visual recovery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveryTime Context triple: [LASIK, recoveryTime, rapid visual recovery]
-
A.
recoveryDuration
chosen
Indicates the length of time required for an entity to return to a normal or functional state after an event, condition, or disruption.
-
B.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
C.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
D.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
-
E.
rehabilitationPeriod
Indicates the span of time during which restorative or corrective measures are applied to return an entity to an acceptable or functional state.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.