Triple
T207305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamb of God |
E4636
|
entity |
| Predicate | petitionFormula |
P10009
|
FINISHED |
| Object | have mercy on us |
—
|
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: have mercy on us | Statement: [Lamb of God, petitionFormula, have mercy on us]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: petitionFormula Context triple: [Lamb of God, petitionFormula, have mercy on us]
-
A.
recurrence
Indicates that an event, condition, or state happens again or repeatedly over time, often after a period of absence or resolution.
-
B.
keyFormula
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
-
C.
recurs
Indicates that an event, condition, or pattern happens again, often repeatedly or at regular intervals, after having occurred before.
-
D.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25e292fdc8190bfd51d8848f9ed58 |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.