Triple
T32241942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakagin Co., Ltd. |
E823638
|
entity |
| Predicate | associatedArchitectureMovement |
P149375
|
FINISHED |
| Object | Metabolism |
E83452
|
NE 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: Metabolism | Statement: [Nakagin Co., Ltd., associatedArchitectureMovement, Metabolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedArchitectureMovement Context triple: [Nakagin Co., Ltd., associatedArchitectureMovement, Metabolism]
-
A.
inArchitecturalMovement
chosen
Indicates that an architectural work, style, or practitioner belongs to or is associated with a specific architectural movement.
-
B.
architecturalInfluence
Indicates that one architectural style, structure, or designer has had a formative impact on the design, style, or features of another.
-
C.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
D.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
-
E.
architecturalContribution
Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
- F. None of above.
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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3bb3b31c81909849bd14969658c3 |
completed | June 14, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:40 a.m.