Triple
T35573491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatia Open Umag |
E1028006
|
entity |
| Predicate | hasQualifyingEvent |
P122415
|
FINISHED |
| Object | ATP singles qualifying |
—
|
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: ATP singles qualifying | Statement: [Croatia Open Umag, hasQualifyingEvent, ATP singles qualifying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualifyingEvent Context triple: [Croatia Open Umag, hasQualifyingEvent, ATP singles qualifying]
-
A.
hasQualifying
Indicates that one entity possesses or meets a specific condition, attribute, or criterion that qualifies it in relation to another entity or context.
-
B.
hasQualifierEvents
chosen
Indicates that certain events serve as qualifiers or contextual modifiers for another event or relationship.
-
C.
qualifyingEvent
Indicates that an event meets specific conditions or criteria that make an entity eligible for a particular status, action, or outcome.
-
D.
hasCoSanctionedEventWith
Indicates that two or more entities have jointly imposed or participated in the same sanction-related event or action.
-
E.
hasCoSanctionedEventsWith
Indicates that two entities have jointly sanctioned or approved the same events.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:04 p.m.