Triple
T16911336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verrückt |
E410199
|
entity |
| Predicate | speedClaim |
P125189
|
FINISHED |
| Object | top speeds over 60 miles 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: top speeds over 60 miles per hour | Statement: [Verrückt, speedClaim, top speeds over 60 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedClaim Context triple: [Verrückt, speedClaim, top speeds over 60 miles per hour]
-
A.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
B.
miracleClaim
Indicates that an entity asserts or reports that a miraculous or supernatural event has occurred.
-
C.
recordClaim
Indicates that an entity formally documents or logs a claim made by another entity or about a particular matter.
-
D.
modalClaim
Indicates that the statement is being made with a modal qualification, such as possibility, necessity, or obligation, rather than as an unqualified factual claim.
-
E.
FrequensClaim
Indicates that an entity frequently asserts, states, or claims something, emphasizing the repeated nature of the claiming action.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3d6be88190bca5e1fdf727141b |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:30 a.m.