Triple
T37475142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albemarle Street literary salon |
E931258
|
entity |
| Predicate | operatedAtAddress |
P837
|
FINISHED |
| Object | 50 Albemarle Street |
—
|
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: 50 Albemarle Street | Statement: [Albemarle Street literary salon, operatedAtAddress, 50 Albemarle Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAtAddress Context triple: [Albemarle Street literary salon, operatedAtAddress, 50 Albemarle Street]
-
A.
operatedAt
chosen
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
B.
operatedFrom
Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
-
C.
operatedNear
Indicates that one entity performed an operation or activity in close physical proximity to another entity.
-
D.
operatedEstablishmentIn
Indicates that an entity ran or managed an establishment located within a specified place or jurisdiction.
-
E.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: May 3, 2026, 4:17 p.m.