Triple
T15602341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Francis Xavier Japanese Catholic Center |
E375063
|
entity |
| Predicate | typeOfParish |
P13874
|
FINISHED |
| Object | national parish |
—
|
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: national parish | Statement: [St. Francis Xavier Japanese Catholic Center, typeOfParish, national parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfParish Context triple: [St. Francis Xavier Japanese Catholic Center, typeOfParish, national parish]
-
A.
hasParishType
chosen
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
B.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
C.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
D.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
E.
civilParishFor
Indicates that one entity is the civil parish to which another entity (such as a place or administrative area) belongs or is assigned.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e6399d88190b2c3e781667666d4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.