Triple
T384175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Moderation |
E8742
|
entity |
| Predicate | questionedAfter |
P4054
|
FINISHED |
| Object | global financial crisis of 2007–2009 |
—
|
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: global financial crisis of 2007–2009 | Statement: [Great Moderation, questionedAfter, global financial crisis of 2007–2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionedAfter Context triple: [Great Moderation, questionedAfter, global financial crisis of 2007–2009]
-
A.
reassessedAfter
chosen
Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
-
B.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
-
C.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
D.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
E.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec422b808190b6ddf747ef939151 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.