Triple
T25318682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadigal Country |
E634817
|
entity |
| Predicate | associatedWithWaterbody |
P85029
|
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: [Gadigal Country, associatedWithWaterbody, Sydney Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWaterbody Context triple: [Gadigal Country, associatedWithWaterbody, Sydney Harbour]
-
A.
hasAssociatedWaterBody
chosen
Indicates that one entity is linked to, or occurs in connection with, a specific body of water such as a river, lake, or sea.
-
B.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
C.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
D.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
E.
connectsBodyOfWater
Indicates a relationship where one entity serves as a link or passage between two bodies of water, allowing them to be joined or interact.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 21, 2026, 1:28 p.m.