Triple
T17064799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne Pool |
E414056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic water feature |
C38759
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic water feature Context triple: [Melbourne Pool, instanceOf, historic water feature]
-
A.
historic fountain
A historic fountain is a decorative water feature of significant age and cultural, artistic, or architectural importance, often serving as a landmark that reflects the history and aesthetics of its period.
-
B.
historic water well
A historic water well is a preserved or documented water source structure from the past that reflects the technological, cultural, and social practices of its time.
-
C.
historic irrigation canal
A historic irrigation canal is a man-made waterway constructed in the past to divert and distribute water for agricultural use, often reflecting the engineering practices and socio-economic conditions of its time.
-
D.
historic stream
A historic stream is a watercourse whose past physical characteristics, flow patterns, and ecological conditions are documented or inferred from historical records, maps, or observations, often differing from its present-day state.
-
E.
historic spring
A historic spring is a naturally occurring water source that has played a significant role in past human activities, culture, or events, and is recognized for its historical importance.
- F. None of above. chosen
Provenance (1 batch)
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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.