Triple
T9743565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amma Memorial |
E236249
|
entity |
| Predicate | commemoratesPersonRole |
P4096
|
FINISHED |
| Object | Indian politician |
—
|
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: Indian politician | Statement: [Amma Memorial, commemoratesPersonRole, Indian politician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesPersonRole Context triple: [Amma Memorial, commemoratesPersonRole, Indian politician]
-
A.
commemoratesRoleAs
chosen
Indicates that something serves to honor or recognize a specific role or position held by an entity.
-
B.
commemoratedPerson
Indicates that the subject serves as a memorial or tribute to the referenced person.
-
C.
memorialRole
Indicates that an entity holds a specific role, capacity, or function in relation to a memorial or commemorative context.
-
D.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
E.
eraCommemorated
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2e5bb081908047e3bf5fe3991c |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.