Triple
T30786234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 『メタボリズムの未来都市』 |
E783961
|
entity |
| Predicate | 関連する建築運動 |
P149375
|
FINISHED |
| Object | メタボリズム |
—
|
NE NERFINISHED |
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.
inArchitecturalMovement
chosen
Indicates that an architectural work, style, or practitioner belongs to or is associated with a specific architectural movement.
-
B.
architectureAssociated
Indicates that there is a relationship or connection between an entity and a particular architectural style, feature, or practice.
-
C.
partOfUrbanPlanningMovement
Indicates that something belongs to, is associated with, or contributes to a specific urban planning movement or school of thought.
-
D.
architecturalConnection
Indicates a structural or design-based relationship linking architectural elements, spaces, or components within a built environment.
-
E.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690097c9c81909858e7d8c15474da |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.