Triple
T32241982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Metabolism movement |
E823639
|
entity |
| Predicate | representativeWork |
P101134
|
FINISHED |
| Object | Nakagin Capsule Tower |
—
|
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: Nakagin Capsule Tower | Statement: [Japanese Metabolism movement, representativeWork, Nakagin Capsule Tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representativeWork Context triple: [Japanese Metabolism movement, representativeWork, Nakagin Capsule Tower]
-
A.
movementRepresentativeWorkOf
chosen
Indicates that a work is considered a key or emblematic example representing a particular movement.
-
B.
workRepresented
Indicates that one entity is a representation (such as a depiction, adaptation, or portrayal) of another work.
-
C.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
-
D.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
E.
notableFeatureOfWork
Indicates that a particular feature, characteristic, or aspect is a notable or distinguishing element of a given work.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 1, 2026, 12:40 a.m.