Triple
T17448661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad God |
E424852
|
entity |
| Predicate | resumedProductionIn |
P44197
|
FINISHED |
| Object | around 2010 |
—
|
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: around 2010 | Statement: [Mad God, resumedProductionIn, around 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumedProductionIn Context triple: [Mad God, resumedProductionIn, around 2010]
-
A.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
B.
restartedFullProductionIn
Indicates that an entity resumed operating at full production capacity starting at a specified time or in a specified period.
-
C.
enteredSeriesProduction
Indicates that an item has transitioned from development or prototype status into regular, large-scale manufacturing or series production.
-
D.
constructionResumed
Indicates that previously halted construction activity on an entity or project has started again.
-
E.
beganCommercialProduction
Indicates that an entity started producing something commercially, marking the commencement of its large-scale or market-oriented production.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513b99908190a6b5833559856c8b |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.