Triple
T242164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anniversary Sale |
E4954
|
entity |
| Predicate | positionInCalendar |
P1818
|
FINISHED |
| Object | mid-year sale event |
—
|
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: mid-year sale event | Statement: [Anniversary Sale, positionInCalendar, mid-year sale event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCalendar Context triple: [Anniversary Sale, positionInCalendar, mid-year sale event]
-
A.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
usesCalendar
chosen
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
workChronologyPosition
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b60ad308190b12f119960a8bde7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.