Triple
T7091029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 貴族院 |
E165192
|
entity |
| Predicate | hasSuccessorLegislature |
P59175
|
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: [貴族院, hasSuccessorLegislature, 日本の国会]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorLegislature Context triple: [貴族院, hasSuccessorLegislature, 日本の国会]
-
A.
successorLegislature
chosen
Indicates that one legislature directly follows and replaces another in a sequence of legislative bodies.
-
B.
successorInLegislativeHierarchy
Indicates that one legislative entity directly follows and replaces another in an ordered hierarchy of legislative positions or authority.
-
C.
hasSuccessorRegime
Indicates that one regime follows and replaces another as its direct successor in a sequence of governing authorities.
-
D.
successorOfficeHolder
Indicates that one office holder directly follows another in occupying the same official position.
-
E.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e53012b081908bf40541d85c82f1 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.