Triple
T7561974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Whinging |
E178813
|
entity |
| Predicate | postalAddressExample |
P41147
|
FINISHED |
| Object | 4 Privet Drive, Little Whinging, Surrey |
—
|
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: 4 Privet Drive, Little Whinging, Surrey | Statement: [Little Whinging, postalAddressExample, 4 Privet Drive, Little Whinging, Surrey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalAddressExample Context triple: [Little Whinging, postalAddressExample, 4 Privet Drive, Little Whinging, Surrey]
-
A.
postalAddressFor
chosen
Indicates that one entity serves as the postal address associated with, or used for sending mail to, another entity.
-
B.
postalAddressInCountry
Indicates that a given postal address is located within the specified country.
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
E.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8f994a48190b8338654d6777654 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:50 p.m.