Triple
T394124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Courts of Japan |
E8942
|
entity |
| Predicate | canReverse |
P9300
|
FINISHED |
| Object | judgments of lower courts |
—
|
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: judgments of lower courts | Statement: [High Courts of Japan, canReverse, judgments of lower courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReverse Context triple: [High Courts of Japan, canReverse, judgments of lower courts]
-
A.
reversed
chosen
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
B.
canReview
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
C.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec77a8a08190b6f96373aa8c1346 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.