Triple
T30931655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarca |
E788006
|
entity |
| Predicate | isPrimaryInflowOf |
P4496
|
FINISHED |
| Object | Lake Garda |
—
|
NE NERFINISHED |
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: Lake Garda | Statement: [Sarca, isPrimaryInflowOf, Lake Garda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryInflowOf Context triple: [Sarca, isPrimaryInflowOf, Lake Garda]
-
A.
hasPrimaryInflow
chosen
Indicates that one entity serves as the main source of inflowing material, energy, or influence into another entity.
-
B.
inflowTo
Indicates that something (such as a fluid, resource, or quantity) flows or moves into a specified target or destination.
-
C.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
D.
secondaryInflow
Indicates an additional, non-primary flow of something (such as water, resources, or information) entering a main system or channel.
-
E.
flowsUltimatelyInto
Indicates that something (typically a fluid, substance, or process) eventually moves or drains into another thing as its final destination, possibly through intermediate stages or paths.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 8:52 p.m.