Triple
T21717183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Rail Reorganization Act of 1973 |
E536059
|
entity |
| Predicate | establishedProcess |
P64843
|
FINISHED |
| Object | Final System Plan for rail service |
—
|
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: Final System Plan for rail service | Statement: [Regional Rail Reorganization Act of 1973, establishedProcess, Final System Plan for rail service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedProcess Context triple: [Regional Rail Reorganization Act of 1973, establishedProcess, Final System Plan for rail service]
-
A.
typicalProcess
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
-
B.
documentedProcess
chosen
Indicates that a process has been formally recorded, described, or specified in documentation.
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
-
E.
establishedToImplement
Indicates that something (such as an organization, system, or structure) was created or set up for the purpose of carrying out or realizing a particular plan, policy, function, or objective.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96babdc81908226ec043dbe7431 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.