Triple
T25905333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Chances |
E652734
|
entity |
| Predicate | hasChaseSequence |
P166600
|
FINISHED |
| Object | massive bridal chase |
—
|
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: massive bridal chase | Statement: [Seven Chances, hasChaseSequence, massive bridal chase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChaseSequence Context triple: [Seven Chances, hasChaseSequence, massive bridal chase]
-
A.
chases
Indicates that one entity actively pursues another, typically moving after it in an attempt to catch or reach it.
-
B.
chasesAcross
Indicates that one entity actively pursues another entity while moving from one side or area to another across some intervening space or surface.
-
C.
hasChicane
Indicates that one entity incorporates or features a chicane (a sharp, S-shaped bend or series of bends), typically in the context of a track, route, or path.
-
D.
nearRecordChase
Indicates a situation where an action or performance closely approaches, but does not surpass, an existing record.
-
E.
carChaseLocation
Indicates the location where a car chase takes place or is occurring.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 22, 2026, 8:27 a.m.