Triple
T410402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litany |
E9476
|
entity |
| Predicate | typicalInvocation |
P6965
|
FINISHED |
| Object | Lord, have mercy |
—
|
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: Lord, have mercy | Statement: [Litany, typicalInvocation, Lord, have mercy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInvocation Context triple: [Litany, typicalInvocation, Lord, have mercy]
-
A.
openingInvocation
chosen
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
-
B.
typicalInstrumentation
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
C.
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).
-
D.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
E.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.