Triple
T30683686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyclopark Gravesend |
E781123
|
entity |
| Predicate | hasRoadCircuitLength |
P151012
|
FINISHED |
| Object | approximately 2.9 km |
—
|
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: approximately 2.9 km | Statement: [Cyclopark Gravesend, hasRoadCircuitLength, approximately 2.9 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadCircuitLength Context triple: [Cyclopark Gravesend, hasRoadCircuitLength, approximately 2.9 km]
-
A.
circuitLength
Indicates the total measured length or distance of a circuit or closed path.
-
B.
approximateCircuitLengthMi
Indicates the approximate total length of a circuit, measured in miles.
-
C.
roadLength
Indicates the measured distance or extent of a road, typically expressed in units of length.
-
D.
approximateCircuitLength
chosen
Indicates that one entity specifies or estimates the circuit length associated with another entity.
-
E.
hasRingRoadLengthApproxKm
Indicates that an entity has a ring road whose length is approximately a specified number of kilometers.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 29, 2026, 8:33 p.m.