Triple
T33797608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Barnet Underground Station |
E866118
|
entity |
| Predicate | openedOnCurrentNetwork |
P192934
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [High Barnet Underground Station, openedOnCurrentNetwork, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedOnCurrentNetwork Context triple: [High Barnet Underground Station, openedOnCurrentNetwork, 1940]
-
A.
isOnNetwork
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
-
B.
openedOnCurrentSite
Indicates that an item, resource, or session was initiated or accessed on the currently active site or domain.
-
C.
networkFounded
Indicates that an organization or entity established or created a particular network.
-
D.
openedInConnectionWith
Indicates that one entity was opened as a direct result of, or in association with, another specific event, action, or entity.
-
E.
inNetwork
Indicates that one entity is within the same defined network, system, or coverage group as another entity, such that network-based interactions or benefits apply between them.
- F. None of above. chosen
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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 1, 2026, 1:46 a.m.