Triple
T1334506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Showa Day |
E28716
|
entity |
| Predicate | establishedAsCurrentForm |
P763
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Showa Day, establishedAsCurrentForm, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsCurrentForm Context triple: [Showa Day, establishedAsCurrentForm, 2007]
-
A.
establishedInCurrentForm
chosen
Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
-
B.
establishedInCurrentFormBy
Indicates that one entity created, organized, or defined another entity in the specific structure or configuration in which it currently exists.
-
C.
originalClaimedForm
Indicates that one entity is asserted to be the initial or first version/form in which another entity was claimed or presented.
-
D.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
E.
standardFormBasedOn
Indicates that one entity’s standard or canonical form is derived from, defined by, or constructed on the basis of another entity.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1eb119881909dd5fbf728d9e8ba |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.