Triple
T26094345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallangatta |
E658218
|
entity |
| Predicate | originalTownSite |
P4380
|
FINISHED |
| Object | now submerged under Lake Hume |
—
|
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: now submerged under Lake Hume | Statement: [Tallangatta, originalTownSite, now submerged under Lake Hume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTownSite Context triple: [Tallangatta, originalTownSite, now submerged under Lake Hume]
-
A.
originalSettlement
Indicates that one entity is the initial or first-established settlement location associated with another entity.
-
B.
originalSiteArea
Indicates the total land area of the site in its initial or pre-modified state.
-
C.
originalSettlementName
Indicates the name by which a settlement was originally known before any later renaming or reclassification.
-
D.
formerSiteOf
chosen
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
E.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 26, 2026, 7:50 p.m.