Triple
T35446984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東洋のルソー |
E1024513
|
entity |
| Predicate | explanation |
P183302
|
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: [東洋のルソー, explanation, フランスの思想家ルソーになぞらえて中江兆民を呼んだ通称]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explanation Context triple: [東洋のルソー, explanation, フランスの思想家ルソーになぞらえて中江兆民を呼んだ通称]
-
A.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
B.
laterExplained
Indicates that an earlier event, statement, or situation is clarified or made understandable by information provided at a subsequent time.
-
C.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
D.
contrastExplanation
Indicates an explanation that highlights differences between two or more entities, ideas, or situations by contrasting them.
-
E.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
- F. None of above. chosen
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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.