Triple
T24320680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liverpool–Southport line |
E612951
|
entity |
| Predicate | networkSector |
P155545
|
FINISHED |
| Object | Northern Line |
—
|
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: Northern Line | Statement: [Liverpool–Southport line, networkSector, Northern Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkSector Context triple: [Liverpool–Southport line, networkSector, Northern Line]
-
A.
networkSection
Indicates that one entity represents a specific section, segment, or subdivision within a larger network structure.
-
B.
networkCenter
Indicates that an entity functions as the central or primary hub within a network, coordinating or connecting other nodes.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
networkArea
Indicates that one entity defines, covers, or is responsible for a specific network area associated with another entity.
-
E.
networkCategory
Indicates the classification or type of network to which an entity or connection belongs.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ab2fa08190bc19c3edc0a1a9b2 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:49 a.m.