Triple
T305155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiwa |
E6280
|
entity |
| Predicate | eraNameSelectionProcess |
P126
|
FINISHED |
| Object | chosen by cabinet from expert-proposed candidates |
—
|
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: chosen by cabinet from expert-proposed candidates | Statement: [Reiwa, eraNameSelectionProcess, chosen by cabinet from expert-proposed candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNameSelectionProcess Context triple: [Reiwa, eraNameSelectionProcess, chosen by cabinet from expert-proposed candidates]
-
A.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
B.
designationProcess
Indicates the process by which an entity is formally assigned, conferred, or recognized with a particular status, role, or designation.
-
C.
selectionProcess
chosen
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
D.
nameChosenToBe
Indicates that an entity has been given or selected to have a particular name.
-
E.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea11c4908190a8723033bdf6f479 |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.