Triple
T9322264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock Heights |
E224296
|
entity |
| Predicate | roadSpeedUnit |
P29841
|
FINISHED |
| Object | kilometres per hour |
—
|
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: kilometres per hour | Statement: [Brock Heights, roadSpeedUnit, kilometres per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadSpeedUnit Context triple: [Brock Heights, roadSpeedUnit, kilometres per hour]
-
A.
typicalRaceDistanceUnit
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
-
B.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
-
C.
unitSystem
chosen
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
-
D.
runwayLengthUnit
Indicates the unit of measurement used to express the length of a runway in the relationship.
-
E.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
- 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f2bd288190bb1556a88d9e90f3 |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.