Triple
T26977883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macchi M.52 |
E679507
|
entity |
| Predicate | recordAttempt |
P170964
|
FINISHED |
| Object | world airspeed record |
—
|
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: world airspeed record | Statement: [Macchi M.52, recordAttempt, world airspeed record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordAttempt Context triple: [Macchi M.52, recordAttempt, world airspeed record]
-
A.
recordAttemptLocation
Indicates that an attempt is made to store or log the specific location where an event or action occurred.
-
B.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
C.
recordRun
Indicates that an entity logs or stores information about a particular execution or run of a process or activity.
-
D.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
E.
recordKeeper
Indicates a relationship where one entity is responsible for maintaining, managing, or preserving official records or documented information about another entity or activity.
- 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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 6:43 a.m.