Triple
T13880416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laing Park |
E333697
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Laing Park |
E333697
|
NE 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: Laing Park | Statement: [Laing Park, namedAfter, Laing Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laing Park Context triple: [Laing Park, namedAfter, Laing Park]
-
A.
Laing Park
chosen
Laing Park is a football ground in Carnoustie, Scotland, best known as the home venue of Carnoustie Panmure F.C.
-
B.
Ramsay Park
Ramsay Park is a public recreational park in Boston that serves the local community with open green space and sports facilities.
-
C.
McElderry Park
McElderry Park is a residential neighborhood in East Baltimore known for its rowhouses, community activism, and ongoing revitalization efforts.
-
D.
Ruskin Park
Ruskin Park is a public green space in the London Borough of Lambeth, known for its landscaped gardens, playgrounds, and views over the city.
-
E.
Redlees Park
Redlees Park is a public green space in Isleworth, Middlesex, England, offering recreational facilities and natural areas for local residents and visitors.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0be8566881908b8902e3cd567669 |
completed | April 14, 2026, 9:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd08c21a48190b4077d5acb4ab658 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:15 p.m.