Triple
T7531752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | लक्ष्मीबाई गोडसे |
E178038
|
entity |
| Predicate | ज्ञात_के_रूप_में |
P310
|
FINISHED |
| Object | नाथूराम गोडसे की माता |
—
|
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: नाथूराम गोडसे की माता | Statement: [लक्ष्मीबाई गोडसे, ज्ञात_के_रूप_में, नाथूराम गोडसे की माता]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ज्ञात_के_रूप_में Context triple: [लक्ष्मीबाई गोडसे, ज्ञात_के_रूप_में, नाथूराम गोडसे की माता]
-
A.
recognizedAs
chosen
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
B.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
knownAsOneOf
Indicates that an entity is recognized or referred to as one member of a specified set of alternative names, labels, or identities.
-
E.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84753fc81908bee2013004ef5fb |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.