Triple
T8687964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amper |
E206210
|
entity |
| Predicate | isNaturalWatercourse |
P84189
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Amper, isNaturalWatercourse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNaturalWatercourse Context triple: [Amper, isNaturalWatercourse, true]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
isOnWatercourse
Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
-
C.
inflowWatercourse
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
D.
isRiverInHydrologicalSense
Indicates that a river, considered as a hydrological feature (its water flow and drainage characteristics), is located within or associated with a specified geographic or hydrological area.
-
E.
sourceOfWatercourse
Indicates that one entity is the origin or starting point from which a watercourse (such as a river or stream) begins or flows.
- F. None of above. chosen
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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5731cf08819082e0cbe0975b70bb |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:33 p.m.