Triple
T12168501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rada lwa |
E289894
|
entity |
| Predicate | invokedThrough |
P1417
|
FINISHED |
| Object | prayers |
—
|
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: prayers | Statement: [Rada lwa, invokedThrough, prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokedThrough Context triple: [Rada lwa, invokedThrough, prayers]
-
A.
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).
-
B.
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.
-
C.
implementedThrough
chosen
Indicates that something is realized, carried out, or made operational by means of a specified method, mechanism, or intermediary.
-
D.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
E.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.