Triple
T30404237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Velinus |
E773433
|
entity |
| Predicate | watercourseInRegion |
P69640
|
FINISHED |
| Object | Velino River |
—
|
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: Velino River | Statement: [Ager Velinus, watercourseInRegion, Velino River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseInRegion Context triple: [Ager Velinus, watercourseInRegion, Velino River]
-
A.
watercourseThroughRegion
chosen
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
-
B.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
C.
feedsWatersThatReach
Indicates that one body of water supplies or contributes flow to other waters that it eventually reaches.
-
D.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
E.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 29, 2026, 8:03 p.m.