Triple
T8666769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seldon Crisis |
E205694
|
entity |
| Predicate | foreseenUsing |
P43685
|
FINISHED |
| Object | psychohistory |
—
|
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: psychohistory | Statement: [Seldon Crisis, foreseenUsing, psychohistory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreseenUsing Context triple: [Seldon Crisis, foreseenUsing, psychohistory]
-
A.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
B.
forecastUsing
chosen
Indicates that one entity generates or derives a forecast by using information, methods, or data from another entity.
-
C.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
D.
foreseesImplementationPeriodOf
Indicates that one entity anticipates or plans the future time frame during which another entity will be implemented or carried out.
-
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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48a34b808190aa9aed9cdb2900e6 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.