Triple
T13646176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surrey Iron Railway |
E326106
|
entity |
| Predicate | parliamentaryActYear |
P39113
|
FINISHED |
| Object | 1801 |
—
|
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: 1801 | Statement: [Surrey Iron Railway, parliamentaryActYear, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentaryActYear Context triple: [Surrey Iron Railway, parliamentaryActYear, 1801]
-
A.
parliamentaryActAssociatedWith
Indicates that there is an association or linkage between an entity and a specific parliamentary act, such as being created, defined, governed, or affected by that legislation.
-
B.
yearEnteredIntoForce
chosen
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
-
C.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
D.
yearOfCouncilReferenced
Indicates that one entity specifies or cites the calendar year in which a particular council took place.
-
E.
dateOfRoyalAssent
Indicates the specific date on which a proposed law or bill formally receives royal assent and thereby becomes law.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.