Triple
T17737076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albemarle Street, London |
E442747
|
entity |
| Predicate | addressOf |
P4379
|
FINISHED |
| Object | John Murray, 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: John Murray, 50 Albemarle Street | Statement: [Albemarle Street, London, addressOf, John Murray, 50 Albemarle Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressOf Context triple: [Albemarle Street, London, addressOf, John Murray, 50 Albemarle Street]
-
A.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
B.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
D.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
E.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478ec48988190a503f9aafeab6d23 |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.