Triple
T17853953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 29 of the Constitution of Japan |
E445880
|
entity |
| Predicate | limitationGround |
P99
|
FINISHED |
| Object | public welfare |
—
|
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: public welfare | Statement: [Article 29 of the Constitution of Japan, limitationGround, public welfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitationGround Context triple: [Article 29 of the Constitution of Japan, limitationGround, public welfare]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
jurisdictionLimit
Indicates the maximum scope or boundary within which an authority, organization, or rule is legally empowered to operate or exercise control.
-
C.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
D.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
E.
movementRestrictions
Indicates limitations, rules, or prohibitions that constrain how, where, or when an entity is allowed to move.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49001d8b881908c8d4efc3d7ff04f |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.