Triple
T12967716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Market Street (Sydney) |
E321306
|
entity |
| Predicate | hasBuildingUseAlongStreet |
P107740
|
FINISHED |
| Object | department stores |
—
|
LITERAL 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: department stores | Statement: [Market Street (Sydney), hasBuildingUseAlongStreet, department stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingUseAlongStreet Context triple: [Market Street (Sydney), hasBuildingUseAlongStreet, department stores]
-
A.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
B.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
C.
hasMainResidentialStreet
Indicates that an entity is associated with or served by a specific primary street used predominantly for residential purposes.
-
D.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
-
E.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
- F. None of above. chosen
Provenance (4 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e5811f481908178fac6d2e0efcd |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:31 p.m.