Triple
T27004625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 金光教 |
E680207
|
entity |
| Predicate | 礼拝施設の名称 |
P161765
|
FINISHED |
| Object | 教会 |
—
|
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: 教会 | Statement: [金光教, 礼拝施設の名称, 教会]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 礼拝施設の名称 Context triple: [金光教, 礼拝施設の名称, 教会]
-
A.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
B.
shrineName
Indicates that an entity has the specified name of a shrine.
-
C.
religiousBuildingInstanceOf
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
D.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
E.
isPartOfEcclesiasticalStructure
Indicates that one ecclesiastical unit, office, or body belongs to, is contained within, or is organizationally subordinate to a larger church or religious governance structure.
- F. None of above. chosen
Provenance (4 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d139f081909f9ca04e04095dba |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 7 a.m.