Triple
T35773940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Open – Women’s doubles |
E1034238
|
entity |
| Predicate | editionInterval |
P97870
|
FINISHED |
| Object | 1 year |
—
|
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: 1 year | Statement: [Australian Open – Women’s doubles, editionInterval, 1 year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editionInterval Context triple: [Australian Open – Women’s doubles, editionInterval, 1 year]
-
A.
typicalIntervalBetweenEditions
chosen
Indicates the usual amount of time that typically elapses between successive editions of the same work.
-
B.
editionTime
Indicates the point or period in time when a particular version or edition of something is created, released, or becomes valid.
-
C.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
D.
appliedToEditionFrequency
Indicates that a particular action, rule, or condition is associated with how often a specific edition occurs or is issued.
-
E.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1fa657c8190b6973f4d60b28e60 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.