Triple
T25387255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McMahons Point |
E631557
|
entity |
| Predicate | mainCommercialStrip |
P95587
|
FINISHED |
| Object | Blues Point Road |
—
|
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: Blues Point Road | Statement: [McMahons Point, mainCommercialStrip, Blues Point Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCommercialStrip Context triple: [McMahons Point, mainCommercialStrip, Blues Point Road]
-
A.
hasCommercialStrip
chosen
Indicates that an area or entity contains or is associated with a zone characterized by a concentration of commercial businesses or retail establishments.
-
B.
isPrimaryCommercialAreaOf
Indicates that one area serves as the main center of commercial activity for another specified place or region.
-
C.
commercialArea
Indicates that the location or region is designated primarily for commercial activities such as businesses, shops, or services.
-
D.
connectsToCommercialArea
Indicates that one location has a direct link, route, or access path to a commercial area.
-
E.
connectsCommercialAreas
Indicates a relationship where one entity links or provides direct access between two or more commercial areas or business districts.
- F. None of above.
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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:47 p.m.