Triple
T10199928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulysses episode "Penelope" |
E238855
|
entity |
| Predicate | settingDate |
P6878
|
FINISHED |
| Object | 17 June 1904 |
—
|
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: 17 June 1904 | Statement: [Ulysses episode "Penelope", settingDate, 17 June 1904]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingDate Context triple: [Ulysses episode "Penelope", settingDate, 17 June 1904]
-
A.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
D.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdee3f3bac8190a63a81edffe7cda7 |
completed | April 2, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:14 p.m.