Triple
T7817752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staten Island Chuck |
E181053
|
entity |
| Predicate | makesPredictionsOn |
P786
|
FINISHED |
| Object | 2 February |
—
|
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: 2 February | Statement: [Staten Island Chuck, makesPredictionsOn, 2 February]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesPredictionsOn Context triple: [Staten Island Chuck, makesPredictionsOn, 2 February]
-
A.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
confirmedPredictionOf
Indicates that a previously made prediction about an entity or event has been verified as accurate or true.
-
C.
sharesProphet
Indicates that two entities recognize or are associated with the same prophet.
-
D.
forecastUsing
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
E.
anticipates
chosen
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf9708bdc8190a5154efe0f96f458 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:40 p.m.