Triple
T51671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Japan |
E1013
|
entity |
| Predicate | containsPrinciple |
P531
|
FINISHED |
| Object | popular sovereignty |
—
|
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: popular sovereignty | Statement: [Constitution of Japan, containsPrinciple, popular sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPrinciple Context triple: [Constitution of Japan, containsPrinciple, popular sovereignty]
-
A.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
B.
violatedPrinciple
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
C.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.