Triple
T11420175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson LiveWire |
E270597
|
entity |
| Predicate | rangeCityApprox |
P99209
|
FINISHED |
| Object | 140 miles |
—
|
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: 140 miles | Statement: [Harley-Davidson LiveWire, rangeCityApprox, 140 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeCityApprox Context triple: [Harley-Davidson LiveWire, rangeCityApprox, 140 miles]
-
A.
hasUrbanProximity
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
B.
cityWide
Indicates that something applies to, affects, or extends across an entire city.
-
C.
coversCity
Indicates that one entity extends over, includes, or geographically encompasses the area of a specified city.
-
D.
marketCity
Indicates that a city serves as a primary marketplace or commercial center for a given region or entity.
-
E.
nearInternationalCity
Indicates that one entity is located geographically close to a city that has international significance, such as serving as a major global hub or capital.
- F. None of above. chosen
Provenance (4 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b20ce08190befc98379b879985 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.