Triple
T35446973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東洋のルソー |
E1024513
|
entity |
| Predicate | refersToPersonMainWork |
P112749
|
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: [東洋のルソー, refersToPersonMainWork, 『三酔人経綸問答』]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonMainWork Context triple: [東洋のルソー, refersToPersonMainWork, 『三酔人経綸問答』]
-
A.
relatedWorkOfPerson
chosen
Indicates that a work (such as a publication, project, or creation) is associated with or produced by a particular person.
-
B.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
C.
authorNotableWork
Indicates that a person is the creator or writer of a specific notable work, such as a book, article, or other significant publication.
-
D.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
E.
refersToPersonKnownFor
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:04 p.m.