Triple
T14357693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊藤博文 |
E356012
|
entity |
| Predicate | 関与した文書 |
P53456
|
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.
legalDocumentInvolvement
chosen
Indicates that an entity is involved with a legal document in some specified role (e.g., author, signer, subject, or recipient).
-
B.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
-
C.
documentsInteractionBetween
Indicates that one entity records, describes, or otherwise captures information about an interaction or event involving another entity.
-
D.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
cameIntoForceRelatedDocument
Indicates that a document became legally effective or operational as a result of, or in connection with, another related document.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8f52ca7881908704eef20228aed3 |
completed | April 14, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:15 a.m.