Triple
T34078630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings Cross |
E873970
|
entity |
| Predicate | streetHub |
P423
|
FINISHED |
| Object | Darlinghurst 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: Darlinghurst Road | Statement: [Kings Cross, streetHub, Darlinghurst Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetHub Context triple: [Kings Cross, streetHub, Darlinghurst Road]
-
A.
streetFunction
Indicates the functional role or primary use of a street within a transportation or urban context (e.g., residential, arterial, commercial access).
-
B.
hubFor
chosen
Indicates that one entity serves as a central node or focal point through which activities, connections, or resources related to another entity are organized or routed.
-
C.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
D.
commonStreetForm
Indicates that two or more street names share the same structural pattern or naming format.
-
E.
communityAddressed
Indicates that a communication, action, or initiative is specifically directed toward or intended for a particular community as its audience or target.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70bd5091c819083228c0e853af49e |
completed | May 3, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.