Triple
T21050275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pendine Sands |
E518558
|
entity |
| Predicate | hasLandSpeedRecordRole |
P51680
|
FINISHED |
| Object | venue for early world land speed records |
—
|
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: venue for early world land speed records | Statement: [Pendine Sands, hasLandSpeedRecordRole, venue for early world land speed records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandSpeedRecordRole Context triple: [Pendine Sands, hasLandSpeedRecordRole, venue for early world land speed records]
-
A.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
B.
worldSpeedRecordContext
Indicates the contextual circumstances (such as event, conditions, or category) under which a world speed record is set or recognized.
-
C.
worldSpeedRecordLocation
chosen
Indicates the location where a world speed record was achieved or officially recorded.
-
D.
peacetimeSpeedRecord
Indicates the maximum speed achieved under non-combat, peacetime conditions, recognized as a record.
-
E.
worldSpeedRecordCountry
Indicates the country in which a given world speed record was achieved or is held.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7a5cf48190939aefaa44db1ddb |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:35 p.m.