Triple
T26300978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiarton Willie |
E661555
|
entity |
| Predicate | predictionMethod |
P159540
|
FINISHED |
| Object | shadow observation |
—
|
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: shadow observation | Statement: [Wiarton Willie, predictionMethod, shadow observation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictionMethod Context triple: [Wiarton Willie, predictionMethod, shadow observation]
-
A.
predictionAlgorithm
Indicates a relationship where an algorithm generates predictions or forecasts about outcomes based on input data or observed patterns.
-
B.
predictionType
Indicates the kind or category of prediction being made about an entity or event.
-
C.
predictionParadigm
chosen
Indicates a methodological framework or approach used to generate, structure, or interpret predictions about future events or states.
-
D.
predictionBy
Indicates that one entity serves as the source or author of a prediction made about another entity or outcome.
-
E.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60eb2b658819086b8ad443c0a9275 |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:15 p.m.