Triple
T677527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic states |
E13110
|
entity |
| Predicate | BalticWayDate |
P6878
|
FINISHED |
| Object | 23 August 1989 |
—
|
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: 23 August 1989 | Statement: [Baltic states, BalticWayDate, 23 August 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BalticWayDate Context triple: [Baltic states, BalticWayDate, 23 August 1989]
-
A.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
C.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
dateInHebrewCalendar
Indicates that a specific date is expressed according to the Hebrew (Jewish) calendar system rather than another calendar.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04c89148190b6330e86697bb37b |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.