Triple
T18884630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sriperumbudur Lok Sabha constituency |
E461926
|
entity |
| Predicate | historicSignificanceOfNamesake |
P4345
|
FINISHED |
| Object | birthplace of Ramanuja |
—
|
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: birthplace of Ramanuja | Statement: [Sriperumbudur Lok Sabha constituency, historicSignificanceOfNamesake, birthplace of Ramanuja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicSignificanceOfNamesake Context triple: [Sriperumbudur Lok Sabha constituency, historicSignificanceOfNamesake, birthplace of Ramanuja]
-
A.
historicallyNamedAfter
Indicates that one entity received its name from another entity at some point in the past.
-
B.
loreSignificance
Indicates that something holds notable importance, relevance, or impact within a fictional world’s backstory, mythology, or overarching narrative.
-
C.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
D.
hasHistoricalSignificance
chosen
Indicates that something possesses notable importance or influence within a historical context or period.
-
E.
historicMonikerReason
Indicates the reason or context for which a particular historic name or moniker was given to an entity.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d3dcec8190a468162c6a4482f6 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.