Triple
T7199977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prayer of the Faithful |
E168714
|
entity |
| Predicate | mayBeLedBy |
P66835
|
FINISHED |
| Object | deacon |
—
|
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: deacon | Statement: [Prayer of the Faithful, mayBeLedBy, deacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeLedBy Context triple: [Prayer of the Faithful, mayBeLedBy, deacon]
-
A.
mayBeHeadedBy
chosen
Indicates that an entity can potentially serve as the leader or head of another entity, but this leadership is not certain or currently established.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
canLeadTo
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
-
D.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
E.
canBeChairOf
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92cc8ac8190a6448b79496a8249 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.