Triple
T10286537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winkies |
E241241
|
entity |
| Predicate | statusAfterRescue |
P93263
|
FINISHED |
| Object | freed |
—
|
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: freed | Statement: [Winkies, statusAfterRescue, freed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterRescue Context triple: [Winkies, statusAfterRescue, freed]
-
A.
rescuedInFormOf
Indicates that one entity is rescued, saved, or recovered specifically in the form, state, or manifestation represented by another entity.
-
B.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
C.
recoveredWithAidFrom
Indicates that an entity returned to a prior or improved state (such as health, function, or condition) as a result of assistance, intervention, or support from another entity.
-
D.
recoveredFrom
Indicates that an entity has returned to a normal or improved state after previously experiencing or being affected by another specified condition, event, or problem.
-
E.
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.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:40 a.m.