Triple
T18191025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moment of Truth |
E435531
|
entity |
| Predicate | recommendationHorizon |
P130166
|
FINISHED |
| Object | 10-year budget window |
—
|
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: 10-year budget window | Statement: [The Moment of Truth, recommendationHorizon, 10-year budget window]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendationHorizon Context triple: [The Moment of Truth, recommendationHorizon, 10-year budget window]
-
A.
recommendation
Indicates that one entity suggests, endorses, or advises another entity as suitable or beneficial for a particular purpose or context.
-
B.
recommendationProcess
Indicates the process by which one entity evaluates options and suggests a preferred choice or course of action to another entity.
-
C.
offersDayPlaces
Indicates that an entity provides or makes available daytime places or slots (e.g., for care, activities, or services) to others.
-
D.
EventHorizonLocations
Indicates the spatial positions or regions where an event horizon exists or is defined.
-
E.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0cf0d7c81908ce0386c52ef601d |
completed | April 19, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.