Triple
T38546169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joti Jot of Guru Gobind Singh |
E924968
|
entity |
| Predicate | hasNumberInGuruLineage |
P125150
|
FINISHED |
| Object | tenth Guru |
—
|
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: tenth Guru | Statement: [Joti Jot of Guru Gobind Singh, hasNumberInGuruLineage, tenth Guru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberInGuruLineage Context triple: [Joti Jot of Guru Gobind Singh, hasNumberInGuruLineage, tenth Guru]
-
A.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
B.
numberOfGurus
Indicates the quantity or count of gurus associated with a given entity or context.
-
C.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
D.
hasBloodline
Indicates that one entity is ancestrally or genetically descended from, or belongs to the lineage of, another entity.
-
E.
hasOrdinalInFamilyLine
chosen
Indicates that an entity holds a specific ordinal position (e.g., first, second, third) within a family lineage or sequence of family members.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.