Triple
T25092862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saleem Sinai |
E628508
|
entity |
| Predicate | storyAddressedTo |
P157937
|
FINISHED |
| Object | Padma |
E628512
|
NE 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: Padma | Statement: [Saleem Sinai, storyAddressedTo, Padma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyAddressedTo Context triple: [Saleem Sinai, storyAddressedTo, Padma]
-
A.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
B.
characterAddressed
Indicates that one character directs speech, communication, or attention specifically toward another character.
-
C.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
D.
addressedFor
Indicates that something is directed, designated, or intended for a particular recipient or target.
-
E.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
- F. None of above. chosen
Provenance (5 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b691bc81908e0a286c32a902e8 |
completed | May 1, 2026, 8:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1048ea21148190b688671c8d8aff35 |
completed | May 22, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 6:24 a.m.