Triple
T25422912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torrumbarry |
E637031
|
entity |
| Predicate | weirPoolName |
P36988
|
FINISHED |
| Object | Torrumbarry Weir Pool |
—
|
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: Torrumbarry Weir Pool | Statement: [Torrumbarry, weirPoolName, Torrumbarry Weir Pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weirPoolName Context triple: [Torrumbarry, weirPoolName, Torrumbarry Weir Pool]
-
A.
poolName
chosen
Indicates the name or label assigned to a specific pool within a broader system or context.
-
B.
originalNameOfPool
Indicates that an entity represents the original or initial name assigned to a specific pool before any renaming or modification.
-
C.
pools
Indicates that one entity combines resources, funds, or elements together with others into a shared collection or common pool.
-
D.
poolLocation
Indicates that one entity is the physical location or site where a particular pool is situated.
-
E.
homePool
Indicates that an entity is associated with or belongs to a primary or default pool, typically used as its main or originating pool.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bd517c819086c0e8e9c2dce972 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:57 p.m.