Triple
T7947968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiltern Hills |
E184542
|
entity |
| Predicate | partiallyTraversedBy |
P49210
|
FINISHED |
| Object | M40 motorway |
—
|
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: M40 motorway | Statement: [Chiltern Hills, partiallyTraversedBy, M40 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyTraversedBy Context triple: [Chiltern Hills, partiallyTraversedBy, M40 motorway]
-
A.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
B.
partiallyCorrespondsTo
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
C.
alsoTraverses
chosen
Indicates that a route, path, or entity passes through or crosses an additional location or segment beyond its primary traversal.
-
D.
partiallySuccessor
Indicates that one entity follows another in a sequence or process, but only to a limited or incomplete extent rather than as a full or direct successor.
-
E.
partiallyCompleted
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:10 p.m.