Triple
T26167393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neir's Tavern |
E654293
|
entity |
| Predicate | hasNameInThePast |
P145623
|
FINISHED |
| Object | The Blue Pump Room |
—
|
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: The Blue Pump Room | Statement: [Neir's Tavern, hasNameInThePast, The Blue Pump Room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInThePast Context triple: [Neir's Tavern, hasNameInThePast, The Blue Pump Room]
-
A.
usesPastFameFor
Indicates that one entity leverages or exploits its previous fame or reputation to gain influence, advantage, or benefit in relation to another entity.
-
B.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
D.
historicalNameUsedIn
chosen
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
E.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 26, 2026, 8:33 p.m.