Triple
T34681974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.D.B. |
E890644
|
entity |
| Predicate | followsPersonalNameIn |
P162309
|
FINISHED |
| Object | Catholic ecclesiastical usage |
—
|
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: Catholic ecclesiastical usage | Statement: [S.D.B., followsPersonalNameIn, Catholic ecclesiastical usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPersonalNameIn Context triple: [S.D.B., followsPersonalNameIn, Catholic ecclesiastical usage]
-
A.
followsInName
Indicates that one entity’s name is derived from, modeled after, or intentionally patterned to follow the naming of another entity.
-
B.
followsNameOf
Indicates that one entity’s name comes immediately after another entity’s name in a specified ordering or sequence.
-
C.
isPersonalNameIn
chosen
Indicates that a personal name appears within or is contained in a specified context, such as a document, text span, or dataset.
-
D.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
E.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 1, 2026, 2:05 a.m.