Triple
T28693096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cincinnati Open |
E729338
|
entity |
| Predicate | leadUpTo |
P116613
|
FINISHED |
| Object | US Open |
—
|
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: US Open | Statement: [Cincinnati Open, leadUpTo, US Open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadUpTo Context triple: [Cincinnati Open, leadUpTo, US Open]
-
A.
isLeadUpTo
Indicates that one event, action, or state serves as a precursor or preparatory phase that directly precedes and contributes to another.
-
B.
endsUp
Indicates that one entity ultimately arrives at, becomes, or results in another state, condition, or location after some process or sequence of events.
-
C.
correctsUpTo
Indicates that one entity adjusts or fixes another entity’s errors or deviations within a specified limit or tolerance.
-
D.
buildsUpTo
chosen
Indicates that one event, action, or state progressively leads toward, prepares for, or culminates in another.
-
E.
canLeadTo
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656acbcd08190b7519a0203609fab |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:37 a.m.