Triple
T7761832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finsbury Park station |
E176039
|
entity |
| Predicate | undergroundServiceBegan |
P60932
|
FINISHED |
| Object | 1904 |
—
|
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: 1904 | Statement: [Finsbury Park station, undergroundServiceBegan, 1904]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundServiceBegan Context triple: [Finsbury Park station, undergroundServiceBegan, 1904]
-
A.
openedAsUndergroundStation
chosen
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
B.
operatedAsUndergroundMovementUntil
Indicates that an organization or group functioned covertly as an underground movement up to a specified point in time.
-
C.
undergroundBranch
Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
-
D.
commuterServiceBegan
Indicates that a commuter transportation service was initiated or began operating between specified locations or entities.
-
E.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
- 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:09 p.m.