Triple
T1394546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dignity Health Sports Park |
E30634
|
entity |
| Predicate | usedForEvent |
P98
|
FINISHED |
| Object | MLS Cup matches |
—
|
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: MLS Cup matches | Statement: [Dignity Health Sports Park, usedForEvent, MLS Cup matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForEvent Context triple: [Dignity Health Sports Park, usedForEvent, MLS Cup matches]
-
A.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37e60388190a8efcb345be7a1b9 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.