Triple
T5387446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Archdiocese of Los Angeles |
E120233
|
entity |
| Predicate | regionOfUSCCB |
P40298
|
FINISHED |
| Object | Region XI |
—
|
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: Region XI | Statement: [Roman Catholic Archdiocese of Los Angeles, regionOfUSCCB, Region XI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfUSCCB Context triple: [Roman Catholic Archdiocese of Los Angeles, regionOfUSCCB, Region XI]
-
A.
isRegionalJurisdictionOf
chosen
Indicates that one entity functions as the governing or administrative authority over a specific geographic region or area.
-
B.
inUSStateRegion
Indicates that one entity is located within, or belongs to, a specific region of a U.S. state.
-
C.
USStateRegion
Indicates that a U.S. state is located within or belongs to a particular geographic region of the United States.
-
D.
federalRegion
Indicates that an entity is located within, administered by, or associated with a specific federal region or federal-level administrative division.
-
E.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f8d81081909174027a4fe640f2 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.