Triple
T2110524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middlesex Guildhall |
E42489
|
entity |
| Predicate | reconstructionForSupremeCourtStart |
P23768
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Middlesex Guildhall, reconstructionForSupremeCourtStart, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstructionForSupremeCourtStart Context triple: [Middlesex Guildhall, reconstructionForSupremeCourtStart, 2007]
-
A.
reconstructionStartYear
chosen
Indicates the calendar year in which a reconstruction process or project began.
-
B.
reconstructionStart
Indicates the point in time or event at which a reconstruction process or activity begins.
-
C.
reconstructionPeriod
Indicates a time span during which something that was damaged, destroyed, or altered is being rebuilt, restored, or substantially repaired.
-
D.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
-
E.
supremeCourtUseFrom
Indicates that a decision, precedent, or legal principle is utilized or drawn upon by a supreme court from a particular source.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb024ce88190a30e1320e53b82bc |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.