Triple
T30785707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | メタボリズム・グループ |
E783949
|
entity |
| Predicate | 思想的特徴 |
P27156
|
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.
展望の特徴
Indicates a characteristic or feature that describes the nature or quality of a prospect, outlook, or future view.
-
B.
themeCharacteristic
Indicates that a characteristic, quality, or property is attributed to or associated with a particular theme.
-
C.
reflectsIdeasOf
Indicates that one entity expresses, mirrors, or embodies the ideas, viewpoints, or conceptual content originating from another entity.
-
D.
ideologicalCharacter
chosen
Indicates a relationship where one entity embodies, expresses, or is defined by a particular ideology or set of ideological traits.
-
E.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes 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_69f68fe8168c8190b083be0e33988b9c |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.