Triple
T19480869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eynsham Lock |
E487377
|
entity |
| Predicate | managesTraffic |
P18246
|
FINISHED |
| Object | pleasure craft |
—
|
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: pleasure craft | Statement: [Eynsham Lock, managesTraffic, pleasure craft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesTraffic Context triple: [Eynsham Lock, managesTraffic, pleasure craft]
-
A.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
B.
trafficManagementStrategy
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
C.
hasTrafficManagement
chosen
Indicates that an entity implements, uses, or is associated with systems or measures for controlling and optimizing traffic flow.
-
D.
trafficManagementGoal
Indicates a goal or objective related to managing, regulating, or optimizing traffic flow and conditions.
-
E.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e634393b8081909f5e4c38b2f1a9b7 |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.