Triple
T22507697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 光の教会 |
E556431
|
entity |
| Predicate | 構造形式 |
P145065
|
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.
構造種別
chosen
Indicates the classification of how something is structured or constructed, distinguishing between different types or forms of structure.
-
B.
使用形態
Indicates a relationship where an entity employs or utilizes a particular form, style, or mode of use.
-
C.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
D.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of another entity.
-
E.
standStructure
Indicates that one entity is a vertical support or upright structural element for another entity.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5dec7c8190bf71ef76a2dfe9a4 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.