Triple
T30444800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishvar Darji |
E774546
|
entity |
| Predicate | relationshipToOmprakashDarji |
P203958
|
FINISHED |
| Object | uncle |
—
|
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 | Statement: [Ishvar Darji, relationshipToOmprakashDarji, uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToOmprakashDarji Context triple: [Ishvar Darji, relationshipToOmprakashDarji, uncle]
-
A.
relationshipTypeWithSohni
Indicates the specific nature or category of the relationship an entity has with Sohni.
-
B.
relationToAkshayKumar
Indicates a specified type of relationship or association that an entity has with Akshay Kumar.
-
C.
relationshipToRama
Indicates the specific familial, social, or other relational connection that an entity has to Rama.
-
D.
relationshipToVrindavan
Indicates the nature or type of connection an entity has to Vrindavan, such as origin, association, or relevance.
-
E.
relationToOdissi
Indicates a relationship or association that something has with Odissi, such as being about, derived from, or connected to the Odissi dance tradition.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a03008316dc8190a9f6faf48d25a4f8 |
completed | May 12, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a030023e66881909ea79f1365ab538a |
completed | May 12, 2026, 10:25 a.m. |
| PDg | Predicate description generation | batch_6a0300826db8819082abc534bae8edb1 |
completed | May 12, 2026, 10:27 a.m. |
Created at: April 29, 2026, 8:08 p.m.