Triple
T29773407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Forum, Norwich |
E755309
|
entity |
| Predicate | publicSquareName |
P49747
|
FINISHED |
| Object | Millennium Plain |
—
|
NE NERFINISHED |
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: Millennium Plain | Statement: [The Forum, Norwich, publicSquareName, Millennium Plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicSquareName Context triple: [The Forum, Norwich, publicSquareName, Millennium Plain]
-
A.
squareName
chosen
Indicates that an entity is identified by or associated with the name of a square (such as a public square or plaza).
-
B.
squareNamedAfter
Indicates that a public square is named in honor of, or derived its name from, a particular person, place, event, or entity.
-
C.
mainSquare
Indicates that a location serves as the primary or central public square of a town or city.
-
D.
squareGivenBy
Indicates that one entity is a square (or square-shaped region) that has been specified, defined, or provided by another entity.
-
E.
squareUse
Indicates that one entity uses or occupies another entity in a square or rectangular configuration, typically implying a grid-like or evenly spaced arrangement.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 8:44 p.m.