Triple
T33244001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Ironmongers |
E851043
|
entity |
| Predicate | Ironmongers’ HallLocation |
P67485
|
FINISHED |
| Object | Barbican area of the City of London |
—
|
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: Barbican area of the City of London | Statement: [Worshipful Company of Ironmongers, Ironmongers’ HallLocation, Barbican area of the City of London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Ironmongers’ HallLocation Context triple: [Worshipful Company of Ironmongers, Ironmongers’ HallLocation, Barbican area of the City of London]
-
A.
hasGuildhall
Indicates that an entity possesses, hosts, or is associated with a guildhall as a dedicated building or facility.
-
B.
knightingLocation
Indicates the place where a knighting ceremony or act of conferring knighthood occurs.
-
C.
hallLocatedNear
Indicates that a hall is situated close to another specified place or entity in physical space.
-
D.
locationOfTavern
Indicates the relationship where a specified place serves as the location of a tavern.
-
E.
hallLocatedAt
chosen
Indicates that a hall is situated at or within a specific location or address.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.