Triple
T12050582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ealing Broadway |
E286903
|
entity |
| Predicate | undergroundServicesBegan |
P60932
|
FINISHED |
| Object | 1879 |
—
|
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: 1879 | Statement: [Ealing Broadway, undergroundServicesBegan, 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundServicesBegan Context triple: [Ealing Broadway, undergroundServicesBegan, 1879]
-
A.
operatedUnderground
Indicates that an entity conducted its activities or operations beneath the surface of the ground, rather than at or above ground level.
-
B.
openedAsUndergroundStation
chosen
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
C.
operatedAsUndergroundMovementUntil
Indicates that an organization or group functioned covertly as an underground movement up to a specified point in time.
-
D.
undergroundBranch
Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
-
E.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.