Triple
T4621228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakan Tanka |
E100988
|
entity |
| Predicate | isInvokedIn |
P8581
|
FINISHED |
| Object | Lakota 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: Lakota prayers | Statement: [Wakan Tanka, isInvokedIn, Lakota prayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInvokedIn Context triple: [Wakan Tanka, isInvokedIn, Lakota 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.
canBeInvokedFrom
Indicates that one entity (such as a function, method, or component) is able to be called or triggered directly from another specified context or entity.
-
C.
isRaisedInContextOf
Indicates that an entity is brought up, discussed, or introduced within a particular situational, thematic, or conversational context.
-
D.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
E.
isReferencedIn
chosen
Indicates that one entity is cited, mentioned, or otherwise referred to within 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e560f481908abb1a97b4ff5795 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.