Triple
T36220868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsworth Bottom Lock |
E1047844
|
entity |
| Predicate | isLowestLockOf |
P91614
|
FINISHED |
| Object | Aylesbury Arm |
—
|
NE NERFINISHED |
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: Aylesbury Arm | Statement: [Marsworth Bottom Lock, isLowestLockOf, Aylesbury Arm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowestLockOf Context triple: [Marsworth Bottom Lock, isLowestLockOf, Aylesbury Arm]
-
A.
isLowestLockOn
chosen
Indicates that a given lock is the one with the lowest (minimum) level or priority among a set of locks.
-
B.
isTopLockOf
Indicates that one object functions as the uppermost locking mechanism for another object or structure.
-
C.
isMajorLockOf
Indicates that one lock functions as the primary or controlling lock for another lock or set of locks.
-
D.
hasLowestForceNumber
Indicates that the subject entity has the smallest (minimum) force number value among a specified set of entities.
-
E.
isLowestCrossingOf
Indicates that one crossing among several possible crossings between entities occurs at the lowest position or level in a given ordering or structure.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b580b2e08190aeb9ef0368e197ba |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.