Triple
T4448598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Maitland |
E96349
|
entity |
| Predicate | hasNearbySuburb |
P41355
|
FINISHED |
| Object | Louth Park |
E109151
|
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: Louth Park | Statement: [East Maitland, hasNearbySuburb, Louth Park]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Louth Park Context triple: [East Maitland, hasNearbySuburb, Louth Park]
-
A.
Louth Park
chosen
Louth Park is a semi-rural residential suburb in the Maitland region of New South Wales, Australia.
-
B.
Ronan Park
Ronan Park is a neighborhood green space in Boston that offers recreational areas, walking paths, and views of the surrounding city.
-
C.
Courtland Park
Courtland Park is a public recreational park located in Reidsville, North Carolina.
-
D.
Ryewood Park
Ryewood Park is a popular scenic garden and recreational green space in the hill station town of Lonavala in Maharashtra, India.
-
E.
Lydney Park
Lydney Park is a historic estate in Gloucestershire, England, known for its Roman temple complex, archaeological remains, and landscaped gardens.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d45b748190b09b7067fc6279b0 |
completed | March 13, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b613895488819083140ae9f0ddba5e |
completed | March 15, 2026, 2:03 a.m. |
Created at: March 12, 2026, 11:32 p.m.