Triple
T12461384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Nemi |
E297800
|
entity |
| Predicate | drainageTunnelPurpose |
P58907
|
FINISHED |
| Object | regulate water level |
—
|
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: regulate water level | Statement: [Lake Nemi, drainageTunnelPurpose, regulate water level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageTunnelPurpose Context triple: [Lake Nemi, drainageTunnelPurpose, regulate water level]
-
A.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
B.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
C.
drainageProject
Indicates that an entity is involved in or designated as a project focused on constructing, improving, or managing systems for removing excess surface or groundwater from an area.
-
D.
drainageOutlet
Indicates that one entity serves as the point where fluids or runoff are discharged or exit from another entity.
-
E.
drainageRole
chosen
Indicates the functional role an entity plays in a drainage system, such as directing, collecting, or removing water or other fluids.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.