Triple
T7082443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglia Route |
E164987
|
entity |
| Predicate | infrastructureManaged |
P15572
|
FINISHED |
| Object | track |
—
|
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: track | Statement: [Anglia Route, infrastructureManaged, track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureManaged Context triple: [Anglia Route, infrastructureManaged, track]
-
A.
infrastructureManager
chosen
Indicates a relationship where one entity is responsible for overseeing, maintaining, or administering the infrastructure of another entity or system.
-
B.
parallelInfrastructure
Indicates that two or more infrastructure elements are arranged or operate in parallel to each other, typically serving similar functions simultaneously.
-
C.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
D.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
E.
isPartOfNetworkManagedBy
Indicates that an entity belongs to and operates under the control or administration of a specific network management authority or system.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e50f133c81908c5f7336fd5bc5d2 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bfcb948190a5ada74fb8c054cb |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:40 p.m.