Triple
T36632674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M&GN |
E904368
|
entity |
| Predicate | jointOwner |
P3498
|
FINISHED |
| Object | Midland Railway |
—
|
NE NERFINISHED |
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: Midland Railway | Statement: [M&GN, jointOwner, Midland Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jointOwner Context triple: [M&GN, jointOwner, Midland Railway]
-
A.
sharesCustodyWith
Indicates that two or more parties jointly hold legal responsibility and decision-making authority for the care and upbringing of the same dependent, typically a child.
-
B.
hasCoOwner
Indicates that an entity shares ownership of something with one or more other entities.
-
C.
sharesOwnershipWith
chosen
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
D.
mayBeManagedJointlyWith
Indicates that an entity can be administered, controlled, or overseen together with another entity as part of a shared or coordinated management arrangement.
-
E.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.