Triple
T1145783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Education Basic Law of Japan |
E23561
|
entity |
| Predicate | majorRevisionDate |
P24446
|
FINISHED |
| Object | 2006-12-22 |
—
|
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: 2006-12-22 | Statement: [Education Basic Law of Japan, majorRevisionDate, 2006-12-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRevisionDate Context triple: [Education Basic Law of Japan, majorRevisionDate, 2006-12-22]
-
A.
majorRevisionYear
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
B.
majorVersion
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
C.
numberOfMajorRevisions
Indicates the count of significant revision events that have occurred for an entity.
-
D.
upgradeDate
Indicates the date on which an entity was upgraded to a newer or improved version.
-
E.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
- F. None of above. chosen
Provenance (4 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc51244c8190bcd533f3e80c8f17 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bbb9fb4c81909dd39c496893c21b |
completed | March 1, 2026, 10:20 p.m. |
Created at: March 1, 2026, 7:44 p.m.