Triple
T13954564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulab Gandhi |
E335620
|
entity |
| Predicate | hasSpousePositionInFamily |
P112393
|
FINISHED |
| Object | eldest son of Mahatma Gandhi |
—
|
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: eldest son of Mahatma Gandhi | Statement: [Gulab Gandhi, hasSpousePositionInFamily, eldest son of Mahatma Gandhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpousePositionInFamily Context triple: [Gulab Gandhi, hasSpousePositionInFamily, eldest son of Mahatma Gandhi]
-
A.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
B.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
C.
spouseFamily
Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
-
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.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of another entity.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e78a4a481908e438745631a43c0 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:17 p.m.