Triple
T37661880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Player (Minecraft) |
E937734
|
entity |
| Predicate | hasSprintSpeedBlocksPerSecond |
P198688
|
FINISHED |
| Object | 5.612 |
—
|
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: 5.612 | Statement: [Player (Minecraft), hasSprintSpeedBlocksPerSecond, 5.612]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSprintSpeedBlocksPerSecond Context triple: [Player (Minecraft), hasSprintSpeedBlocksPerSecond, 5.612]
-
A.
hasSprintRace
Indicates that an event or competition includes a sprint-format race as part of its structure or schedule.
-
B.
isSprintEvent
Indicates that an event is classified as a sprint, typically involving short-distance, high-speed competition.
-
C.
isSprint
Indicates that an entity represents a short, time-boxed iteration or development cycle within a larger project or process.
-
D.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
E.
sprintRace
Indicates a competitive running event over a short distance where participants race to finish in the fastest time.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
| PDg | Predicate description generation | batch_69fefb13eb288190bcfae0541cfd7b98 |
completed | May 9, 2026, 9:15 a.m. |
Created at: May 3, 2026, 4:18 p.m.