Triple
T9963790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hull and Barnsley Railway |
E195630
|
entity |
| Predicate | dateBecamePartOf |
P50534
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [Hull and Barnsley Railway, dateBecamePartOf, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateBecamePartOf Context triple: [Hull and Barnsley Railway, dateBecamePartOf, 1923]
-
A.
incorporatedIntoOnDate
chosen
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
B.
foundingDateOfInvolvement
Indicates the date on which an entity first became involved in, or began its participation in, a particular relationship, organization, or activity.
-
C.
allianceMembershipStartDate
Indicates the date on which an entity formally begins its membership in an alliance.
-
D.
joinedInYear
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
-
E.
admittedToUnionOn
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a union or federation on a specific date.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71a33b48190a18c1a9023f249d2 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.