Triple
T26374637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 81 of the Constitution of Japan |
E660860
|
entity |
| Predicate | reviewModel |
P161703
|
FINISHED |
| Object | concrete judicial review model in Japan |
—
|
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: concrete judicial review model in Japan | Statement: [Article 81 of the Constitution of Japan, reviewModel, concrete judicial review model in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewModel Context triple: [Article 81 of the Constitution of Japan, reviewModel, concrete judicial review model in Japan]
-
A.
reviewType
Indicates the specific category or kind of review associated with an item, action, or relationship.
-
B.
reviewBody
Indicates the textual content of a review that expresses an evaluator’s opinions, comments, or feedback about something.
-
C.
reviewMethod
Indicates the method or process by which something is examined, evaluated, or reviewed.
-
D.
reviewFormat
Indicates the specific structure, style, or medium in which a review is presented or delivered.
-
E.
reviewOf
Indicates that one entity is a critical or evaluative assessment that is about or directed toward another entity.
- F. None of above. chosen
Provenance (4 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 26, 2026, 11 p.m.