Triple
T17625028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timavo River |
E429816
|
entity |
| Predicate | subterraneanFlowDirection |
P75396
|
FINISHED |
| Object | towards Gulf of Trieste |
—
|
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: towards Gulf of Trieste | Statement: [Timavo River, subterraneanFlowDirection, towards Gulf of Trieste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subterraneanFlowDirection Context triple: [Timavo River, subterraneanFlowDirection, towards Gulf of Trieste]
-
A.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
B.
pilgrimFlowDirection
Indicates the direction in which pilgrims move or travel along a route, path, or within a pilgrimage site.
-
C.
hasDirectionOfFlow
Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
-
D.
waterwayDirection
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
E.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbb2a348190982658d495c81da0 |
completed | April 19, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.