Triple
T30977890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiora River basin |
E789278
|
entity |
| Predicate | mouthReceivesWatersAt |
P124067
|
FINISHED |
| Object | Tyrrhenian Sea |
E24776
|
NE 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 Sea | Statement: [Fiora River basin, mouthReceivesWatersAt, Tyrrhenian Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthReceivesWatersAt Context triple: [Fiora River basin, mouthReceivesWatersAt, Tyrrhenian Sea]
-
A.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
B.
mouthOfWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
C.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage system.
-
D.
riverMouthAt
chosen
Indicates that the mouth or endpoint of a river is located at a specified place or geographic feature.
-
E.
riverMouthBasin
Indicates that a river’s mouth lies within or drains into a particular drainage basin.
- F. None of above.
Provenance (4 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29182dc8ac8190b7f7f9a71aa9ee0e |
completed | June 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:55 p.m.