Triple

T28120347
Position Surface form Disambiguated ID Type / Status
Subject Albemarle Street E710765 entity
Predicate hasStreetNumber P40967 FINISHED
Object 21 Albemarle Street
21 Albemarle Street is a notable address in London’s Mayfair district, historically associated with prominent literary and cultural institutions.
E1803100 NE 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: 21 Albemarle Street | Statement: [Albemarle Street, hasStreetNumber, 21 Albemarle Street]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 21 Albemarle Street
Triple: [Albemarle Street, hasStreetNumber, 21 Albemarle Street]
Generated description
21 Albemarle Street is a notable address in London’s Mayfair district, historically associated with prominent literary and cultural institutions.

Provenance (5 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_69ef9b72f63081909dfbc2c1ddae86c6 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f640f73d9481909a07574a7db092eb completed May 2, 2026, 6:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15c933587c819083839265507781ee completed May 26, 2026, 4:24 p.m.
NEDg Description generation batch_6a15ca9b9b888190a98c57af571fe49d completed May 26, 2026, 4:30 p.m.
NED2 Entity disambiguation (via description) batch_6a15cc3cef0c8190b7b5d6316dc2a9ff completed May 26, 2026, 4:37 p.m.
Created at: April 27, 2026, 9:16 p.m.