Triple
T1087043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Litany |
E24075
|
entity |
| Predicate | typicalResponse |
P24080
|
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: [Great Litany, typicalResponse, Lord, have mercy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResponse Context triple: [Great Litany, typicalResponse, Lord, have mercy]
-
A.
globalResponse
Indicates a reaction, policy, or set of actions taken collectively at an international or worldwide level in response to a particular event or situation.
-
B.
responseTool
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
-
C.
responseFrom
Indicates that one entity is the originator or source of a response directed to another entity or request.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b963161081908a523c8d63871652 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.