Triple
T17426973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overall |
E423763
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object | Park Overall |
—
|
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: Park Overall | Statement: [Overall, hasNotableBearer, Park Overall]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Park Overall Context triple: [Overall, hasNotableBearer, Park Overall]
-
A.
Park
chosen
Park is a common surname of Scottish origin borne by various notable individuals, including figures in early professional golf.
-
B.
Home Park
Home Park is a historic royal deer park and landscaped estate surrounding Windsor Castle in Berkshire, England.
-
C.
Home Park
Home Park is a football stadium in Plymouth, England, best known as the long-time home ground of Plymouth Argyle F.C.
-
D.
Home Park
Home Park is a historic royal deer park surrounding Hampton Court Palace in southwest London, known for its expansive lawns, wildlife, and formal landscapes.
-
E.
Welcome Park
Welcome Park is a small historical park in Philadelphia dedicated to William Penn and the city’s founding, featuring exhibits and a model of the original city plan.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e448fcbf54819091babed0b9b05716 |
completed | April 19, 2026, 3:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.