Triple
T28828598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune |
E727980
|
entity |
| Predicate | cancelledIn |
P7625
|
FINISHED |
| Object | around 2000 |
—
|
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: around 2000 | Statement: [Neptune, cancelledIn, around 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancelledIn Context triple: [Neptune, cancelledIn, around 2000]
-
A.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
B.
cancellation
chosen
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
C.
cancels
Indicates that one entity invalidates, nullifies, or stops the effect, operation, or scheduled occurrence of another entity or action.
-
D.
canceledBefore
Indicates that one event, reservation, or commitment was canceled at a time earlier than another specified event or reference point.
-
E.
canceledAfter
Indicates that one event or action was canceled at a point in time occurring after another specified event or action.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 6:36 a.m.