Triple
T33431660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton Miracle |
E856145
|
entity |
| Predicate | decisiveTryTime |
P41440
|
FINISHED |
| Object | final minutes of the match |
—
|
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: final minutes of the match | Statement: [Brighton Miracle, decisiveTryTime, final minutes of the match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveTryTime Context triple: [Brighton Miracle, decisiveTryTime, final minutes of the match]
-
A.
decisiveTryScorer
Indicates that an entity scored a try that decisively determined the outcome of a match or competition.
-
B.
decidingScoreTime
chosen
Indicates the point in time at which a decisive or game-determining score occurs.
-
C.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
D.
decisive
Indicates that one entity makes a conclusive choice or determination that resolves a situation or outcome between entities.
-
E.
decisiveDrive
Indicates a strong, determined motivation that leads an entity to take clear, firm action toward a goal.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:36 a.m.