Triple
T11406025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JNR |
E270239
|
entity |
| Predicate | reformOutcome |
P99138
|
FINISHED |
| Object | division into regional JR companies |
—
|
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: division into regional JR companies | Statement: [JNR, reformOutcome, division into regional JR companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformOutcome Context triple: [JNR, reformOutcome, division into regional JR companies]
-
A.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
B.
isPartOfReform
Indicates that an action, measure, or component belongs to, contributes to, or is included within a broader reform initiative or process.
-
C.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
-
D.
councilOutcome
Indicates the result or decision produced by a council after its deliberation or proceedings.
-
E.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014c820c81908538ba4a08e13230 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.