Triple
T7108171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter and Paul Fast |
E165641
|
entity |
| Predicate | fastDiscipline |
P74945
|
FINISHED |
| Object | regulated by local church canons |
—
|
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: regulated by local church canons | Statement: [Peter and Paul Fast, fastDiscipline, regulated by local church canons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastDiscipline Context triple: [Peter and Paul Fast, fastDiscipline, regulated by local church canons]
-
A.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
-
B.
fastSeverity
Indicates the level or intensity of severity associated with something that is fast or time-critical.
-
C.
speed
Indicates the rate at which an entity moves or changes position over time.
-
D.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
-
E.
isFastPaced
Indicates that an activity, event, or process proceeds quickly with rapid progression and little downtime.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5bbd4e481909e0948d01c6b15f4 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:42 p.m.