Triple
T24021232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Open |
E594825
|
entity |
| Predicate | cutImplementedAfterRound |
P25030
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Italian Open, cutImplementedAfterRound, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cutImplementedAfterRound Context triple: [Italian Open, cutImplementedAfterRound, 2]
-
A.
hasCutAfterRound
chosen
Indicates that an entity is eliminated or removed from participation after a specified round.
-
B.
cutBy
Indicates that one entity is divided, severed, or shaped as a result of another entity performing a cutting action on it.
-
C.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
D.
cutOff
Indicates that one entity causes another entity to be disconnected, interrupted, or severed from a source, flow, or continuation.
-
E.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:47 p.m.