Triple
T34308237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paper Church in Kobe |
E880368
|
entity |
| Predicate | isTemporaryStructure |
P50685
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Paper Church in Kobe, isTemporaryStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTemporaryStructure Context triple: [Paper Church in Kobe, isTemporaryStructure, true]
-
A.
isTemporary
chosen
Indicates that the relationship, state, or condition holds only for a limited or non-permanent duration.
-
B.
isPermanentStructure
Indicates that the entity is a fixed, enduring construction that is not intended to be temporary or movable.
-
C.
temporaryStructureFor
Indicates that one entity serves as a non-permanent or provisional structure intended to support, house, or substitute for another entity.
-
D.
isTemporaryDesignation
Indicates that a given designation or label is intended to be used only for a limited time and is not the entity’s permanent or final designation.
-
E.
originalTemporaryStructureUnveiledOn
Indicates that the date or event specified is when the original temporary structure was first publicly revealed or opened.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.