Triple
T22440738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 皇室会議 |
E554747
|
entity |
| Predicate | 開催要件 |
P30361
|
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.
conveningCondition
chosen
Indicates the circumstances or requirements under which a meeting, gathering, or formal session is initiated or brought together.
-
B.
celebrationRequires
Indicates that a particular celebration depends on or necessitates the presence, occurrence, or provision of something.
-
C.
hasOpeningCondition
Indicates that a relationship or action is subject to a specific initial condition that must be met before it can begin or take effect.
-
D.
参加組織・会議
Indicates participation in or membership of an organization or meeting.
-
E.
participantRequirement
Indicates that a certain condition, qualification, or constraint must be met by an entity in order to participate in a specified activity, event, or relationship.
- 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.