Triple
T23497463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese law |
E571739
|
entity |
| Predicate | codificationPeriod |
P123517
|
FINISHED |
| Object | Meiji era |
—
|
NE NERFINISHED |
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: Meiji era | Statement: [Japanese law, codificationPeriod, Meiji era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codificationPeriod Context triple: [Japanese law, codificationPeriod, Meiji era]
-
A.
timePeriodOfCodification
chosen
Indicates the time period during which something was formally codified or set into an official, systematic form.
-
B.
timeOfCodification
Indicates the specific point in time at which something (such as a rule, law, or concept) was formally codified or recorded.
-
C.
implementationPeriod
Indicates the time span during which a plan, project, or agreement is actively carried out or executed.
-
D.
codifiedThrough
Indicates that something is formally established, expressed, or made authoritative by means of a specific codification process, document, or legal/institutional mechanism.
-
E.
codificationEvent
Indicates an event in which rules, principles, or information are formally organized and recorded into a structured, codified system.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e0c5a48190badb8303f40f6180 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.