Triple
T14682241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalal-ud-din Khalji |
E344816
|
entity |
| Predicate | relationshipToAlauddinKhalji |
P115308
|
FINISHED |
| Object | uncle and father-in-law |
—
|
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: uncle and father-in-law | Statement: [Jalal-ud-din Khalji, relationshipToAlauddinKhalji, uncle and father-in-law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAlauddinKhalji Context triple: [Jalal-ud-din Khalji, relationshipToAlauddinKhalji, uncle and father-in-law]
-
A.
relationshipToTimur
Indicates the type or nature of the relationship that one entity has to Timur.
-
B.
relationToKhalidIbnAlWalid
Indicates a relationship or association that an entity has with Khalid ibn al-Walid.
-
C.
relationToNurJahan
Indicates a relationship or connection that an entity has specifically to Nur Jahan.
-
D.
roleInAkbarsLife
Indicates the specific role, position, or significance that one entity held in relation to Akbar’s life.
-
E.
relationshipToKingShahryar
Indicates the type or nature of a person's relationship to King Shahryar, such as familial, marital, or social connection.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.