Triple
T26279571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Amen |
E660665
|
entity |
| Predicate | roleInParticipation |
P98934
|
FINISHED |
| Object | invites active participation of the faithful |
—
|
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: invites active participation of the faithful | Statement: [Great Amen, roleInParticipation, invites active participation of the faithful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInParticipation Context triple: [Great Amen, roleInParticipation, invites active participation of the faithful]
-
A.
engagementRole
chosen
Indicates the specific function, capacity, or responsibility an entity assumes within a particular engagement or interaction.
-
B.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
C.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
roleInClub
Indicates that an entity holds a specific position or function within a particular club.
-
E.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 26, 2026, 9:59 p.m.