Triple
T14562828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emissario del Lago Albano |
E341708
|
entity |
| Predicate | watercourseDestination |
P88669
|
FINISHED |
| Object | Tyrrhenian drainage basin |
—
|
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: Tyrrhenian drainage basin | Statement: [Emissario del Lago Albano, watercourseDestination, Tyrrhenian drainage basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseDestination Context triple: [Emissario del Lago Albano, watercourseDestination, Tyrrhenian drainage basin]
-
A.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
B.
waterwayDestination
chosen
Indicates that a waterway leads to, flows into, or terminates at a specified destination.
-
C.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38afa8881909c9151b7620949ae |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.