Triple
T2394275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Breviary |
E47611
|
entity |
| Predicate | requiresUseBy |
P22634
|
FINISHED |
| Object | Latin-rite clergy (pre–Vatican II) |
—
|
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: Latin-rite clergy (pre–Vatican II) | Statement: [Roman Breviary, requiresUseBy, Latin-rite clergy (pre–Vatican II)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresUseBy Context triple: [Roman Breviary, requiresUseBy, Latin-rite clergy (pre–Vatican II)]
-
A.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
B.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
C.
requiresShowingBy
Indicates that one entity must be demonstrated, displayed, or presented by another entity as a necessary condition or step.
-
D.
areUsedBy
chosen
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
E.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc87827d88190bb2351a688e6de32 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.