Triple
T17176945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Docks and Inland Waterways Executive |
E416883
|
entity |
| Predicate | managedInfrastructureType |
P121871
|
FINISHED |
| Object | docks |
—
|
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: docks | Statement: [Docks and Inland Waterways Executive, managedInfrastructureType, docks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedInfrastructureType Context triple: [Docks and Inland Waterways Executive, managedInfrastructureType, docks]
-
A.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
B.
overseesInfrastructureType
chosen
Indicates that one entity is responsible for supervising, managing, or regulating a particular type or category of infrastructure.
-
C.
infrastructureManager
Indicates a relationship where one entity is responsible for overseeing, maintaining, or administering the infrastructure of another entity or system.
-
D.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
E.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another 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_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.