Triple
T17177017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railway Executive |
E416885
|
entity |
| Predicate | controlledAsset |
P113316
|
FINISHED |
| Object | railway infrastructure in Great Britain |
—
|
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: railway infrastructure in Great Britain | Statement: [Railway Executive, controlledAsset, railway infrastructure in Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledAsset Context triple: [Railway Executive, controlledAsset, railway infrastructure in Great Britain]
-
A.
controlsAssetsFor
Indicates that one entity has authority to manage or direct the assets owned by another entity.
-
B.
protectedAsset
Indicates that one entity serves as a safeguarded or defended resource in relation to another entity.
-
C.
asset
chosen
Indicates that one entity is a valuable resource, item, or property owned, controlled, or beneficially used by another entity.
-
D.
securedControlOver
Indicates that one entity has successfully obtained and established authoritative control or dominance over another entity or resource.
-
E.
assetType
Indicates the specific category or classification of an asset within a broader asset framework 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0e14e08190901b1fbccc9322ae |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.