Triple
T33593877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koenigsegg One:1 |
E860503
|
entity |
| Predicate | recordAttempts |
P170964
|
FINISHED |
| Object | top-speed runs on test tracks |
—
|
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: top-speed runs on test tracks | Statement: [Koenigsegg One:1, recordAttempts, top-speed runs on test tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordAttempts Context triple: [Koenigsegg One:1, recordAttempts, top-speed runs on test tracks]
-
A.
recordAttempt
chosen
Indicates an action where an attempt or trial is logged or stored as a record, typically capturing that the attempt occurred and possibly its outcome.
-
B.
attemptNumber
Indicates the specific ordinal count of attempts made for a given action or process.
-
C.
completionAttemptsBy
Indicates that a specific entity’s completion attempts are attributed to or performed by another entity.
-
D.
launchAttemptCount
Indicates the number of times a launch has been attempted for the associated entity or event.
-
E.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:41 a.m.