Triple
T27190839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woollahra |
E683468
|
entity |
| Predicate | harbourProximity |
P42191
|
FINISHED |
| Object | Sydney Harbour |
—
|
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: Sydney Harbour | Statement: [Woollahra, harbourProximity, Sydney Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: harbourProximity Context triple: [Woollahra, harbourProximity, Sydney Harbour]
-
A.
hasNearbyHarbor
chosen
Indicates that one location has a harbor situated close to it in geographic proximity.
-
B.
associatedHarbour
Indicates a relationship where a place, route, or maritime entity is linked to or served by a particular harbour.
-
C.
harbourUse
Indicates how a harbour is used or purposed, such as for specific activities, functions, or types of maritime operations.
-
D.
harbourSystem
Indicates a relationship where one entity serves as a harbor or port system that accommodates, services, or supports another entity (such as ships, goods, or maritime operations).
-
E.
nearIsland
Indicates that one entity is located close to or in the vicinity of an island.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625abb50081908345dd4cff9fee49 |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:32 a.m.