Triple
T22177441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomson River (Victoria) |
E548084
|
entity |
| Predicate | isImpededBy |
P85838
|
FINISHED |
| Object | Thomson Dam |
—
|
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: Thomson Dam | Statement: [Thomson River (Victoria), isImpededBy, Thomson Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isImpededBy Context triple: [Thomson River (Victoria), isImpededBy, Thomson Dam]
-
A.
isBarrierTo
chosen
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
B.
hasImpedance
Indicates that one entity possesses or is characterized by a specific electrical impedance value or property in relation to another.
-
C.
isDifficultToAccessBecauseOf
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
-
D.
obstacles
Indicates that one entity presents barriers, hindrances, or impediments that block or restrict another entity’s progress, action, or interaction.
-
E.
isDifficultToAccess
Indicates that reaching, using, or obtaining the referenced entity requires significant effort, obstacles, or special conditions.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6d03488190b29872ff3f436237 |
completed | April 28, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.