Triple
T12756356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City and South London Railway |
E304869
|
entity |
| Predicate | closingDateAsIndependentCompany |
P102297
|
FINISHED |
| Object | 1913-01-01 |
—
|
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: 1913-01-01 | Statement: [City and South London Railway, closingDateAsIndependentCompany, 1913-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingDateAsIndependentCompany Context triple: [City and South London Railway, closingDateAsIndependentCompany, 1913-01-01]
-
A.
closedAsIndependentCompany
chosen
Indicates that an entity has ceased operations as an independent company, typically due to closure, merger, or acquisition.
-
B.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
-
C.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
D.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
E.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.