Triple
T5928552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluebird K7 |
E131875
|
entity |
| Predicate | setWorldWaterSpeedRecordTimes |
P30976
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Bluebird K7, setWorldWaterSpeedRecordTimes, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWorldWaterSpeedRecordTimes Context triple: [Bluebird K7, setWorldWaterSpeedRecordTimes, 7]
-
A.
setWorldRecordsIn
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
-
B.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
C.
setWorldRecordCount
chosen
Indicates the number of times an entity has achieved or set a world record.
-
D.
heldWorldRecordTime
Indicates that an entity achieved and maintained the fastest known performance time in a specific event or activity, recognized as the official world record for a period.
-
E.
wasWorldRecordFor
Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.