Triple
T23087851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowndes Square |
E575660
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Hyde 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: Hyde Park | Statement: [Lowndes Square, near, Hyde Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hyde Park Context triple: [Lowndes Square, near, Hyde Park]
-
A.
Hyde Park
Hyde Park is a historic central public park in Sydney, Australia, known for its tree-lined avenues, monuments, and recreational green space.
-
B.
Hyde Park
chosen
Hyde Park is one of London’s largest and most famous royal parks, known for its expansive green spaces, recreational activities, and historic landmarks like Speakers’ Corner and the Serpentine.
-
C.
Hyde Park
Hyde Park is an affluent, tree-lined suburb and shopping district in Sandton, Johannesburg, known for its luxury residences and upscale retail center.
-
D.
Hyde Park
Hyde Park is a small city in northern Utah known as a residential community within the Logan metropolitan area.
-
E.
Hyde Park
Hyde Park is a historic and upscale residential and shopping district located just southwest of downtown Tampa, Florida.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da7c54c81908b62d04ab1811b06 |
completed | April 29, 2026, 4:48 a.m. |
Created at: April 17, 2026, 3:57 p.m.