Triple
T34187821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhai Daya Singh |
E877009
|
entity |
| Predicate | gaveHeadOnCallOf |
P178502
|
FINISHED |
| Object | Guru Gobind Singh |
—
|
NE NERFINISHED |
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: Guru Gobind Singh | Statement: [Bhai Daya Singh, gaveHeadOnCallOf, Guru Gobind Singh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveHeadOnCallOf Context triple: [Bhai Daya Singh, gaveHeadOnCallOf, Guru Gobind Singh]
-
A.
tookHeadOf
Indicates that one entity removed or claimed the head (literal or symbolic) of another entity.
-
B.
hasGivenCallFor
Indicates that one entity has issued or made a formal call, request, or appeal for another entity or action.
-
C.
assignedHead
Indicates that one entity has been designated as the primary leader or person in charge of another entity (such as a group, department, or organization).
-
D.
isOnCallFor
Indicates that one entity is currently designated as available and responsible to respond to needs, requests, or emergencies for another entity.
-
E.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head 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_69f349af20a4819089ac24d28f2d8112 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.