Triple
T8241242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heckfield |
E192538
|
entity |
| Predicate | hasApproximateDistanceToHook |
P37106
|
FINISHED |
| Object | about 4 miles north |
—
|
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: about 4 miles north | Statement: [Heckfield, hasApproximateDistanceToHook, about 4 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDistanceToHook Context triple: [Heckfield, hasApproximateDistanceToHook, about 4 miles north]
-
A.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
-
B.
isCloseTo
Indicates that one entity is physically or conceptually near another, within a relatively short distance or range.
-
C.
approximateDistanceFrom
chosen
Indicates an estimated or rough measure of how far one entity is from another.
-
D.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
E.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783e13648190abf34eb8c244ea17 |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.