Triple
T36620005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pawitter Kaur |
E903706
|
entity |
| Predicate | spouseHeldOfficeNumber |
P197342
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Pawitter Kaur, spouseHeldOfficeNumber, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseHeldOfficeNumber Context triple: [Pawitter Kaur, spouseHeldOfficeNumber, 7]
-
A.
spouseOfOfficeholderNumber
Indicates that one entity is the spouse of a specific officeholder identified by their ordinal number in holding a particular office.
-
B.
spouseNumberOfTermsInOffice
Indicates the number of distinct terms in office that the spouse of the referenced entity has served.
-
C.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
D.
spouseLaterOffice
Indicates that one person’s spouse held a particular office or position at a later time than the person in question.
-
E.
officeHoldersNumber
Indicates the number of individuals who hold a particular office or position.
- F. None of above. chosen
Provenance (4 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: May 3, 2026, 4:11 p.m.