Triple
T24902711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Rankings |
E623621
|
entity |
| Predicate | updateDay |
P53180
|
FINISHED |
| Object | typically Monday |
—
|
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: typically Monday | Statement: [ATP Rankings, updateDay, typically Monday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateDay Context triple: [ATP Rankings, updateDay, typically Monday]
-
A.
updateDayOfWeek
chosen
Indicates changing or setting the day of the week value associated with an entity or record.
-
B.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
C.
updatedEvery
Indicates that something is refreshed or brought up to date at a regular, specified interval.
-
D.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
E.
updateFor
Indicates that one entity is modified or refreshed in response to changes or conditions associated with another entity.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:27 a.m.