Triple
T186489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihon-koku Kenpō |
E3991
|
entity |
| Predicate | declaresInArticle9 |
P2948
|
FINISHED |
| Object | renunciation of war |
—
|
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: renunciation of war | Statement: [Nihon-koku Kenpō, declaresInArticle9, renunciation of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaresInArticle9 Context triple: [Nihon-koku Kenpō, declaresInArticle9, renunciation of war]
-
A.
article9Provision
chosen
Indicates a relationship where a specific legal or contractual element is identified as a provision contained within Article 9 of a larger document or agreement.
-
B.
containsArticle
Indicates that one entity includes or holds an article (such as a written piece, item, or document) as part of its contents.
-
C.
canDeclare
Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
-
D.
keyArticle
Indicates that an article is a primary or central reference for understanding, supporting, or defining another entity or topic.
-
E.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594809288190b3d3b1283e7e0d00 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.