Triple
T11256245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 春の叙勲 |
E266444
|
entity |
| Predicate | 関連文書 |
P19741
|
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.
linkedDocument
chosen
Indicates that one document is associated with or references another document in a meaningful way.
-
B.
cameIntoForceRelatedDocument
Indicates that a document became legally effective or operational as a result of, or in connection with, another related document.
-
C.
関連主題
Indicates that there exists a thematically or contextually related subject connected to the given entity.
-
D.
documentsInteractionBetween
Indicates that one entity records, describes, or otherwise captures information about an interaction or event involving another entity.
-
E.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e935b85c819085e1abf2dd4099c5 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.