Triple
T31788336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocklington Canal |
E811392
|
entity |
| Predicate | primaryFunctionAtOpening |
P58201
|
FINISHED |
| Object | agricultural freight transport |
—
|
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: agricultural freight transport | Statement: [Pocklington Canal, primaryFunctionAtOpening, agricultural freight transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionAtOpening Context triple: [Pocklington Canal, primaryFunctionAtOpening, agricultural freight transport]
-
A.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
B.
primaryUseStart
Indicates the point in time or event at which the primary use or main function of something begins.
-
C.
primaryFunctionInPractice
Indicates that an entity serves as the main or most important function or role within a given practical context or real-world usage.
-
D.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
-
E.
primaryOperation
chosen
Indicates the main or most important operation performed or used by an entity in a given context.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:38 p.m.