Triple
T181151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastham Lock |
E3878
|
entity |
| Predicate | isAt |
P6308
|
FINISHED |
| Object | western end of Manchester Ship Canal |
—
|
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: western end of Manchester Ship Canal | Statement: [Eastham Lock, isAt, western end of Manchester Ship Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAt Context triple: [Eastham Lock, isAt, western end of Manchester Ship Canal]
-
A.
isAbout
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
-
B.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
C.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
- F. None of above. chosen
Provenance (4 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575e7c7c819095167d8a862c255a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.