Triple
T11084180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi State vs. Connecticut (2017 NCAA Women's Final Four) |
E262075
|
entity |
| Predicate | decisiveMomentTime |
P41440
|
FINISHED |
| Object | end of overtime |
—
|
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: end of overtime | Statement: [Mississippi State vs. Connecticut (2017 NCAA Women's Final Four), decisiveMomentTime, end of overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveMomentTime Context triple: [Mississippi State vs. Connecticut (2017 NCAA Women's Final Four), decisiveMomentTime, end of overtime]
-
A.
exposureTime
Indicates the duration for which a subject or object is exposed to a particular condition, influence, or medium.
-
B.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
C.
timeOfInitiation
Indicates the specific point in time at which an action, event, or process begins.
-
D.
timeDefinite
Indicates that the associated event or state occurs at a clearly specified, fixed point or interval in time.
-
E.
decidingScoreTime
chosen
Indicates the point in time at which a decisive or game-determining score occurs.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c0cc3081908448cfb26c08daf5 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.