Triple
T17951745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svaha |
E448846
|
entity |
| Predicate | invocationWord |
P129868
|
FINISHED |
| Object | “svāhā” |
—
|
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: “svāhā” | Statement: [Svaha, invocationWord, “svāhā”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invocationWord Context triple: [Svaha, invocationWord, “svāhā”]
-
A.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
-
B.
invocationFlag
Indicates that an entity has been marked or configured to be invoked, often controlling whether a particular action, method, or process should be executed.
-
C.
exhortedBy
Indicates that one entity is strongly urged, encouraged, or admonished to act or think in a certain way by another entity.
-
D.
openingVerb
Indicates that an entity performs the initial or primary action that begins an event, process, or interaction.
-
E.
invocationType
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afac95048190a5d1ef012899c62b |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.