Triple
T4088912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Recession recovery |
E87657
|
entity |
| Predicate | relativeSpeed |
P13562
|
FINISHED |
| Object | slower than typical postwar U.S. recoveries |
—
|
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: slower than typical postwar U.S. recoveries | Statement: [Great Recession recovery, relativeSpeed, slower than typical postwar U.S. recoveries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSpeed Context triple: [Great Recession recovery, relativeSpeed, slower than typical postwar U.S. recoveries]
-
A.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
speed
chosen
Indicates the rate at which an entity moves or changes position over time.
-
D.
relativeLength
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
E.
velocityRelativeToSun
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.