Triple
T17245901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notting Hill |
E418623
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Holland Park |
—
|
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: Holland Park | Statement: [Notting Hill, adjacentTo, Holland Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holland Park Context triple: [Notting Hill, adjacentTo, Holland Park]
-
A.
Holland Park
chosen
Holland Park is a leafy, affluent district and public park in west London known for its elegant townhouses, landscaped gardens, and cultural attractions.
-
B.
Holborn Park
Holborn Park is a public green space in Berkeley, California, offering local residents recreational areas and outdoor amenities.
-
C.
Green Park
Green Park is a public park in Kanpur, India, historically significant enough to lend its name to the nearby Green Park Stadium.
-
D.
Green Park
Green Park is a central London royal park known for its open lawns, mature trees, and tranquil atmosphere between Buckingham Palace and Piccadilly.
-
E.
Green Park
Green Park is a Delhi Metro station in South Delhi serving the Green Park and nearby Hauz Khas and Safdarjung areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
Created at: April 10, 2026, 5:39 a.m.