Triple
T16661455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exton |
E404868
|
entity |
| Predicate | hasEstate |
P8997
|
FINISHED |
| Object | Exton Park |
E625202
|
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: Exton Park | Statement: [Exton, hasEstate, Exton Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Exton Park Context triple: [Exton, hasEstate, Exton Park]
-
A.
Exton Park
chosen
Exton Park is a public recreational park in Exton, Pennsylvania, featuring open green spaces, walking trails, and community amenities.
-
B.
Courtland Park
Courtland Park is a public recreational park located in Reidsville, North Carolina.
-
C.
Howden Park
Howden Park is a public recreational area in the Howden district, typically offering green space, walking paths, and community leisure facilities.
-
D.
Eldridge Park
Eldridge Park is a historic amusement and recreation park in Elmira, New York, known for its classic rides, lakeside setting, and family-friendly attractions.
-
E.
Morton Park
Morton Park is a public recreational park located in Fairview Park, Ohio.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfee5448190bb44c4dadba5dcbd |
completed | April 18, 2026, 12:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084d091e0819088a98ef4aa775d07 |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:18 a.m.