Triple
T8915855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bononia |
E212293
|
entity |
| Predicate | isLocatedOnWatercourse |
P58979
|
FINISHED |
| Object | near the Reno river |
—
|
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: near the Reno river | Statement: [Bononia, isLocatedOnWatercourse, near the Reno river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedOnWatercourse Context triple: [Bononia, isLocatedOnWatercourse, near the Reno river]
-
A.
isOnWatercourse
chosen
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
B.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
C.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
-
D.
isNaturalWatercourse
Indicates that one entity is a naturally formed flowing body of water (such as a river or stream), rather than an artificial or man-made channel.
-
E.
isInWaterwaySystem
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660f6a088190b0af829ea809d8ad |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.