Triple
T18540414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishta Devata |
E453082
|
entity |
| Predicate | mayBeAssignedBy |
P132073
|
FINISHED |
| Object | a 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: a guru | Statement: [Ishta Devata, mayBeAssignedBy, a guru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAssignedBy Context triple: [Ishta Devata, mayBeAssignedBy, a guru]
-
A.
mayBeBoundBy
Indicates that one entity is potentially subject to being constrained, restricted, or obligated by another entity (such as a rule, agreement, or condition), without asserting that this binding actually occurs.
-
B.
canBeAssignedTo
Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
-
C.
canBeReassignedBy
Indicates that one entity has the authority or ability to change or transfer another entity’s assignment or allocation.
-
D.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
E.
requiresAssignment
Indicates that one entity depends on another entity being assigned or allocated before it can proceed, function, or be considered valid.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b64178819082861a03fd067095 |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.