Triple
T23497475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese law |
E571739
|
entity |
| Predicate | layJudgeSystemIntroduced |
P152619
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Japanese law, layJudgeSystemIntroduced, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layJudgeSystemIntroduced Context triple: [Japanese law, layJudgeSystemIntroduced, 2009]
-
A.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
B.
hasJudgeFrom
Indicates that an entity has a judge whose origin, affiliation, or source is from a specified place or organization.
-
C.
hasJudges
Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
-
D.
hasJudgeType
Indicates that an entity is associated with a specific category or type of judge.
-
E.
judgesAre
Indicates that one entity serves as a judge or evaluator of 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e0c5a48190badb8303f40f6180 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:05 p.m.