Triple
T6658622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olenyok River |
E151411
|
entity |
| Predicate | breaksUpIn |
P72143
|
FINISHED |
| Object | late May |
—
|
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: late May | Statement: [Olenyok River, breaksUpIn, late May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breaksUpIn Context triple: [Olenyok River, breaksUpIn, late May]
-
A.
brokenUpAt
Indicates that a romantic or close relationship between two entities ended at a specific time or date.
-
B.
breaksUpWith
Indicates that one entity ends a romantic or intimate relationship with another entity.
-
C.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
-
D.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
E.
breakUpSeason
Indicates the time of year or season during which a romantic relationship ends or a breakup occurs.
- F. None of above. chosen
Provenance (4 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.