Triple
T33093961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Father Dolan |
E846858
|
entity |
| Predicate | enforcesDisciplineAt |
P139006
|
FINISHED |
| Object | Clongowes Wood College |
—
|
NE NERFINISHED |
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: Clongowes Wood College | Statement: [Father Dolan, enforcesDisciplineAt, Clongowes Wood College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesDisciplineAt Context triple: [Father Dolan, enforcesDisciplineAt, Clongowes Wood College]
-
A.
attractsDiscipline
Indicates a relationship where one entity draws or brings about discipline, order, or self-control in another entity.
-
B.
regulatesDiscipline
Indicates that one entity establishes or enforces rules, standards, or controls governing the conduct or discipline of another entity.
-
C.
disciplinarianOf
chosen
Indicates that one entity holds and exercises strict authority or control over another, enforcing rules and discipline.
-
D.
strongInDiscipline
Indicates that an entity possesses a high level of strength, skill, or proficiency in a particular discipline or field.
-
E.
earlyDiscipline
Indicates that an entity begins or enforces discipline at an unusually early time or stage.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.