Triple
T30785673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | メタボリズム |
E783948
|
entity |
| Predicate | 代表的理論家 |
P55473
|
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.
theoreticalLeader
Indicates a relationship where one entity is regarded as the leader in theory or principle, but does not necessarily hold or exercise actual leadership in practice.
-
B.
notableTheorist
chosen
Indicates that the subject is recognized as a significant or influential theorist in relation to the object or specified field.
-
C.
memberOfSchoolOfThought
Indicates that an entity adheres to, participates in, or is affiliated with a particular school of thought or intellectual tradition.
-
D.
theoreticalFigure
Indicates a relationship where one entity is a conceptual or hypothetical figure associated with, referenced by, or used in the theoretical context of another entity.
-
E.
roleInTheory
Indicates the specific function, position, or contribution that an entity has within a particular theory or theoretical framework.
- 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.