Triple
T1087049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Litany |
E24075
|
entity |
| Predicate | includesPetitionsFor |
P14344
|
FINISHED |
| Object | peace from above |
—
|
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: peace from above | Statement: [Great Litany, includesPetitionsFor, peace from above]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPetitionsFor Context triple: [Great Litany, includesPetitionsFor, peace from above]
-
A.
containsPetition
chosen
Indicates that one entity includes or holds a petition within it, either as content or as a component.
-
B.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
participatesInPoliticsOf
Indicates involvement or active engagement by one entity in the political processes, affairs, or governance activities of another entity.
-
D.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
E.
eligibleParties
Indicates that certain entities are qualified or permitted to participate in, benefit from, or be subject to a specified agreement, process, or condition.
- 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_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. |
Created at: March 1, 2026, 7:42 p.m.