Triple
T27441808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mildenhall Road |
E690955
|
entity |
| Predicate | currentNetwork |
P66218
|
FINISHED |
| Object | National Rail |
—
|
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: National Rail | Statement: [Mildenhall Road, currentNetwork, National Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentNetwork Context triple: [Mildenhall Road, currentNetwork, National Rail]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
intendedNetwork
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
-
C.
networkStatus
Indicates the current operational state or connectivity condition of a network or networked system.
-
D.
inNetwork
chosen
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.
-
E.
originalNetworkName
Indicates the name of the network from which something (e.g., data, content, or a connection) originally came.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 12:45 p.m.