Triple
T7200165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Christ the King Sovereign Priest |
E168718
|
entity |
| Predicate | layBranch |
P12340
|
FINISHED |
| Object | oblates |
—
|
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: oblates | Statement: [Institute of Christ the King Sovereign Priest, layBranch, oblates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layBranch Context triple: [Institute of Christ the King Sovereign Priest, layBranch, oblates]
-
A.
branchPoint
Indicates a point in a process, structure, or path where a single preceding element splits into two or more alternative continuations or options.
-
B.
trainedBranch
Indicates that one entity has provided training or instruction to a specific branch or subdivision of another entity.
-
C.
branchNetwork
chosen
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
-
D.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
E.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92cc8ac8190a6448b79496a8249 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.