Triple
T5908248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shyam Charan Murmu |
E131394
|
entity |
| Predicate | spouseOfOfficeHolderNumber |
P58368
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Shyam Charan Murmu, spouseOfOfficeHolderNumber, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfOfficeHolderNumber Context triple: [Shyam Charan Murmu, spouseOfOfficeHolderNumber, 15]
-
A.
spouseOfOfficeHolderJurisdiction
Indicates that one person is the spouse of a public office holder, with the relationship specifically tied to the jurisdiction in which that office is held.
-
B.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
C.
spouseCount
chosen
Indicates the number of spouses an entity has.
-
D.
spouseOfHead
Indicates that one person is the married partner of the individual who holds the position of head (e.g., head of a household, organization, or state).
-
E.
spouseOfCountry
Indicates that an entity is the spouse or marital partner of a person who is associated with, represents, or is from a specified country.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.