Triple
T37234650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muirhouse |
E923534
|
entity |
| Predicate | regenerationBeganInDecade |
P96888
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Muirhouse, regenerationBeganInDecade, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regenerationBeganInDecade Context triple: [Muirhouse, regenerationBeganInDecade, 2010s]
-
A.
restoredInDecade
Indicates that an entity was restored or brought back to a prior or improved condition during a specified decade.
-
B.
redevelopedInDecade
chosen
Indicates that an entity was redeveloped during a specified decade.
-
C.
revivedInDecade
Indicates that an entity was brought back into use, popularity, or active existence during a specified decade.
-
D.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
E.
developmentStartDecade
Indicates the decade during which the development or creation of an entity was initiated.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.