Triple
T22440521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 長和殿 |
E554742
|
entity |
| Predicate | 関連主体 |
P84787
|
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.
所属事業者
Indicates that one entity is the business operator or company to which another entity belongs or is affiliated.
-
B.
subjectRelation
chosen
Indicates that one entity stands in a specified relational role or connection to another entity.
-
C.
administrativeBodyInvolved
Indicates that an administrative or governing body participates in, oversees, or is otherwise involved in the referenced action, process, or relationship.
-
D.
hostsOrganizationRelevantToRelations
Indicates that a host entity is associated with an organization that is pertinent or significant to the relationships or interactions being modeled.
-
E.
concernedOrganization
Indicates that an organization is involved with, responsible for, or affected by the referenced matter, issue, or activity.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.