Triple
T14058354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowy Mountains Hydro-electric Power Act 1949 |
E338276
|
entity |
| Predicate | relatedProjectType |
P108759
|
FINISHED |
| Object | inter-basin water transfer |
—
|
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: inter-basin water transfer | Statement: [Snowy Mountains Hydro-electric Power Act 1949, relatedProjectType, inter-basin water transfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedProjectType Context triple: [Snowy Mountains Hydro-electric Power Act 1949, relatedProjectType, inter-basin water transfer]
-
A.
relatedToProject
Indicates that an entity has a connection or association with a specific project, without specifying the exact nature of that involvement.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
associatedWithResourceProjects
chosen
Indicates a relationship where an entity is linked or connected to specific resource-related projects, such as their development, management, or use.
-
D.
associatedWorkType
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
E.
parentProject
Indicates that one project serves as the direct higher-level or containing project in relation to another project.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8e6d008190af8892f34c5cefbd |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.