Triple
T23497466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese law |
E571739
|
entity |
| Predicate | postwarConstitutionEnforced |
P140596
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Japanese law, postwarConstitutionEnforced, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postwarConstitutionEnforced Context triple: [Japanese law, postwarConstitutionEnforced, 1947]
-
A.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
B.
restoredConstitution
chosen
Indicates that an entity has brought a constitution back into force or its previous state after it was suspended, altered, or invalidated.
-
C.
afterRepublicBecame
Indicates that one event, state, or condition occurred subsequent to the time when a republic was established or came into existence.
-
D.
servedUnderConstitution
Indicates that an individual held an official position or exercised authority while a specific constitution was in force and governing their role.
-
E.
statusAfterWWII
Indicates the condition, role, or classification an entity had following the end of World War II.
- 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.