Triple
T5807455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shūgiin |
E128779
|
entity |
| Predicate | sessionTypes |
P983
|
FINISHED |
| Object | ordinary sessions |
—
|
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: ordinary sessions | Statement: [Shūgiin, sessionTypes, ordinary sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sessionTypes Context triple: [Shūgiin, sessionTypes, ordinary sessions]
-
A.
sessionType
chosen
Indicates the classification or category of a particular session based on its purpose, format, or context.
-
B.
sessionOf
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
-
C.
slotType
Indicates the classification or category assigned to a particular slot or position within a structure, system, or sequence.
-
D.
sessionNotation
Indicates a notation or labeling that is specifically associated with a particular session or occurrence of an event.
-
E.
submissionTypes
Indicates the categories or formats in which something can be submitted or has been submitted within a given context.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b17417081908779741b9bfbb720 |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.