Triple
T33177582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ronco River |
E849224
|
entity |
| Predicate | hasMouthNearCity |
P45963
|
FINISHED |
| Object | Ravenna |
—
|
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: Ravenna | Statement: [Ronco River, hasMouthNearCity, Ravenna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMouthNearCity Context triple: [Ronco River, hasMouthNearCity, Ravenna]
-
A.
hasMouthPositionRelativeToCity
chosen
Indicates the spatial position of a river’s mouth in relation to a specified city.
-
B.
majorCityNearMouth
Indicates that a major city is located close to the mouth (outflow point) of a river.
-
C.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
-
D.
hasPortNearMouth
Indicates that an entity possesses a port or opening located close to its mouth region.
-
E.
passesNearCity
Indicates that the path, route, or trajectory of one entity goes close to, but not necessarily through, a specified city.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 1, 2026, 1:29 a.m.