Triple
T37188966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meon Valley Railway |
E921396
|
entity |
| Predicate | operatingCompanyAtGrouping |
P62102
|
FINISHED |
| Object | Southern Railway |
E102970
|
NE 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: Southern Railway | Statement: [Meon Valley Railway, operatingCompanyAtGrouping, Southern Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingCompanyAtGrouping Context triple: [Meon Valley Railway, operatingCompanyAtGrouping, Southern Railway]
-
A.
operatedByCompanyInstanceOf
Indicates that an operation or activity is carried out by a specific company that is an instance of a particular company type or class.
-
B.
operatingCompanyAbbreviation
Indicates that the object is an abbreviated or shortened form of the name of the company that operates the subject.
-
C.
railwayCompanyGroup
Indicates that one entity is a group or consortium that includes or controls the other entity as a railway company.
-
D.
operatedByCompany
chosen
Indicates that an entity is run, managed, or controlled by a specific company.
-
E.
operatedByCompanyHeadquarteredIn
Indicates that an entity is operated by a company whose headquarters is located in a specified place.
- F. None of above.
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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4043b2801881908e14c2458bc9c998 |
completed | June 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: May 3, 2026, 4:15 p.m.