Triple
T24128605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macchi M.39 |
E597878
|
entity |
| Predicate | setWorldSpeedRecord |
P38164
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [Macchi M.39, setWorldSpeedRecord, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWorldSpeedRecord Context triple: [Macchi M.39, setWorldSpeedRecord, 1926]
-
A.
setWorldRecordsIn
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
-
B.
setWorldRecordLocation
Indicates the place where a world record was set or achieved.
-
C.
worldRecordSetOn
chosen
Indicates that a world record was achieved or established on a specific date or occasion.
-
D.
setWorldRecordCompetition
Indicates that an entity achieved a world record performance within the context of a specific competition.
-
E.
worldRecordSet
Indicates that an entity has achieved and established the best performance ever recorded in the world for a particular activity, event, or measurable criterion.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df751c94819084652a89c7c2cc1f |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:22 p.m.