Triple
T18392808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svir |
E449778
|
entity |
| Predicate | hasCanalInfrastructure |
P128244
|
FINISHED |
| Object | locks and dams |
—
|
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: locks and dams | Statement: [Svir, hasCanalInfrastructure, locks and dams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanalInfrastructure Context triple: [Svir, hasCanalInfrastructure, locks and dams]
-
A.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
B.
hasMajorCanal
Indicates that one entity possesses or contains a primary canal or main waterway associated with it.
-
C.
hasIndustrialCanalFeatures
chosen
Indicates that an entity possesses physical or structural characteristics associated with industrial canals, such as engineered waterways, locks, channels, or related infrastructure used for industrial purposes.
-
D.
hasBranchCanals
Indicates that an entity possesses or is connected to one or more subsidiary or secondary canals branching off from a main canal.
-
E.
hasAqueduct
Indicates that one entity possesses, contains, or is equipped with an aqueduct that serves or passes through it.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518435cf481908393c1eb2b4ba659 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.