Triple
T32244613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speed (franchise) |
E823712
|
entity |
| Predicate | hasAwardWinningPart |
P173878
|
FINISHED |
| Object | Speed (1994 film) |
—
|
NE NERFINISHED |
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: Speed (1994 film) | Statement: [Speed (franchise), hasAwardWinningPart, Speed (1994 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAwardWinningPart Context triple: [Speed (franchise), hasAwardWinningPart, Speed (1994 film)]
-
A.
hasAwardUnit
Indicates that an award is associated with, measured in, or granted in terms of a specific unit (such as a quantity, category, or subdivision).
-
B.
hasJuryAward
Indicates that an entity has received a decision or compensation determined by a jury.
-
C.
hasAwardItem
Indicates that an entity possesses, is associated with, or has been granted a specific award item.
-
D.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
E.
hasAwardField
Indicates that an entity’s award is associated with or categorized under a particular field or domain.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc32ea2c8190b1cb870c14b05821 |
completed | May 3, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:40 a.m.