Triple
T27693202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman River |
E698210
|
entity |
| Predicate | hasCatchmentTown |
P41298
|
FINISHED |
| Object | Croydon, Queensland |
—
|
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: Croydon, Queensland | Statement: [Norman River, hasCatchmentTown, Croydon, Queensland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatchmentTown Context triple: [Norman River, hasCatchmentTown, Croydon, Queensland]
-
A.
hasMajorTownInCatchment
chosen
Indicates that a catchment area includes at least one major town within its geographic or service coverage.
-
B.
hasCatchmentAuthority
Indicates that an entity holds official responsibility or authority over managing and regulating a particular catchment area.
-
C.
hasUrbanCatchment
Indicates that an entity is associated with a catchment area that is characterized as urban.
-
D.
isInCatchment
Indicates that one entity lies within the geographic or service area covered or served by another entity.
-
E.
hasCatchmentAreaLocation
Indicates that a catchment area is geographically located in or associated with a specific place or region.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 2:52 p.m.