Triple
T35828528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 106 Wimpole Street |
E1035721
|
entity |
| Predicate | isNotableAddressOn |
P184161
|
FINISHED |
| Object | Wimpole Street |
—
|
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: Wimpole Street | Statement: [106 Wimpole Street, isNotableAddressOn, Wimpole Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotableAddressOn Context triple: [106 Wimpole Street, isNotableAddressOn, Wimpole Street]
-
A.
isNotable
Indicates that an entity is recognized as significant, prominent, or worthy of attention within a particular context or domain.
-
B.
isNotableNameOf
Indicates that a name is widely recognized or distinguished as a significant identifier for the referenced entity.
-
C.
hasNotableIdentity
Indicates that an entity is recognized for a specific, distinguished role, status, or identity that makes it notable.
-
D.
notablePresence
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
-
E.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
- F. None of above. chosen
Provenance (4 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.