Triple
T24931349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronit Krushka |
E618995
|
entity |
| Predicate | returnsFor |
P157799
|
FINISHED |
| Object | father's funeral |
—
|
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: father's funeral | Statement: [Ronit Krushka, returnsFor, father's funeral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsFor Context triple: [Ronit Krushka, returnsFor, father's funeral]
-
A.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
B.
returnedFor
Indicates that an entity has been sent, given, or brought back in response to, or on behalf of, another entity or prior action.
-
C.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
D.
returnsTo
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
E.
returnedAs
Indicates that one entity is given back or sent back to another entity or to its original source, typically as the outcome of a prior transfer, request, or operation.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:30 a.m.