Triple
T9627562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore 1965 paper |
E232506
|
entity |
| Predicate | typeOfPrediction |
P79173
|
FINISHED |
| Object | empirical technological trend |
—
|
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: empirical technological trend | Statement: [Moore 1965 paper, typeOfPrediction, empirical technological trend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPrediction Context triple: [Moore 1965 paper, typeOfPrediction, empirical technological trend]
-
A.
predictionType
chosen
Indicates the kind or category of prediction being made about an entity or event.
-
B.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
C.
predictionAlgorithm
Indicates a relationship where an algorithm generates predictions or forecasts about outcomes based on input data or observed patterns.
-
D.
confirmedPredictionOf
Indicates that a previously made prediction about an entity or event has been verified as accurate or true.
-
E.
typeOfProphecy
Indicates the specific category or kind of prophecy that a given prophetic statement or vision belongs to.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.