Triple
T14114311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Japanese general election |
E339721
|
entity |
| Predicate | campaignPeriodLength |
P90129
|
FINISHED |
| Object | approximately 12 days |
—
|
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: approximately 12 days | Statement: [1996 Japanese general election, campaignPeriodLength, approximately 12 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignPeriodLength Context triple: [1996 Japanese general election, campaignPeriodLength, approximately 12 days]
-
A.
campaignDuration
chosen
Indicates the length of time over which a campaign runs from its start to its end.
-
B.
registrationPeriod
Indicates the time span during which registration for something is open or valid.
-
C.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
D.
agingPeriod
Indicates the length of time something is allowed or intended to mature or age before reaching its final or usable state.
-
E.
policyPeriod
Indicates the time span during which a particular policy is in effect or valid.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.