Triple
T1159106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Vespers |
E24453
|
entity |
| Predicate | mayBeAssistedBy |
P11876
|
FINISHED |
| Object | deacons |
—
|
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: deacons | Statement: [Great Vespers, mayBeAssistedBy, deacons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAssistedBy Context triple: [Great Vespers, mayBeAssistedBy, deacons]
-
A.
assistsWith
chosen
Indicates that one entity helps or supports another entity in performing or accomplishing a specific task, activity, or objective.
-
B.
facilitatedBy
Indicates that an action, process, or relationship occurs or is made easier through the assistance, support, or enabling role of a particular agent or mechanism.
-
C.
mayBeChallengedBy
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcad47a08190895769611798f67f |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.