Triple
T4513735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gayatri Mantra |
E102107
|
entity |
| Predicate | invocationOf |
P57113
|
FINISHED |
| Object | three worlds |
—
|
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: three worlds | Statement: [Gayatri Mantra, invocationOf, three worlds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invocationOf Context triple: [Gayatri Mantra, invocationOf, three worlds]
-
A.
invocationType
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
-
B.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
C.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
D.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
agreementInvoked
Indicates that a formal agreement or contract has been activated, called upon, or put into effect between the related entities.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd572402f481908151f7899bc96306 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.