Triple
T38160955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serco Docklands |
E953016
|
entity |
| Predicate | maintainedInfrastructureType |
P121871
|
FINISHED |
| Object | tracks |
—
|
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: tracks | Statement: [Serco Docklands, maintainedInfrastructureType, tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedInfrastructureType Context triple: [Serco Docklands, maintainedInfrastructureType, tracks]
-
A.
preservesInfrastructureType
Indicates that an action or process maintains or keeps unchanged the type or category of infrastructure involved.
-
B.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
-
C.
overseesInfrastructureType
chosen
Indicates that one entity is responsible for supervising, managing, or regulating a particular type or category of infrastructure.
-
D.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
E.
typicalInfrastructure
Indicates that something is part of the standard or commonly expected infrastructure associated with a given context or entity.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:21 p.m.