Triple
T29541286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzmaurice River estuary |
E749505
|
entity |
| Predicate | hasConnectivityWith |
P845
|
FINISHED |
| Object | Fitzmaurice River catchment |
—
|
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: Fitzmaurice River catchment | Statement: [Fitzmaurice River estuary, hasConnectivityWith, Fitzmaurice River catchment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectivityWith Context triple: [Fitzmaurice River estuary, hasConnectivityWith, Fitzmaurice River catchment]
-
A.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
requiresConnectivityUndirected
Indicates that an undirected (bidirectional) connectivity relationship must exist between the involved entities.
-
C.
hasTeleconnectionsWith
Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
-
D.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
E.
connectivityFor
Indicates a relationship where one entity provides, enables, or defines network or communication connectivity for another entity.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
Created at: April 28, 2026, 5:02 p.m.