Triple
T25708931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eden river system |
E644674
|
entity |
| Predicate | hasConfluenceAt |
P56926
|
FINISHED |
| Object | Carlisle |
E24767
|
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: Carlisle | Statement: [Eden river system, hasConfluenceAt, Carlisle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConfluenceAt Context triple: [Eden river system, hasConfluenceAt, Carlisle]
-
A.
hasConfluencePointAt
Indicates that two or more flows, paths, or entities meet and merge at a specific point.
-
B.
hasConcurrenceFrom
Indicates that an action, decision, or proposal is supported or agreed upon by another party or authority.
-
C.
startsAfterConfluenceOf
Indicates that one entity begins at a point located downstream from, and subsequent to, the confluence where two or more other entities merge.
-
D.
hasMajorConfluence
Indicates that a watercourse joins with another watercourse at a significant or primary confluence point.
-
E.
isConfluenceAtCity
chosen
Indicates that the confluence (meeting point) of two or more water bodies occurs at or within the specified city.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ec97cf6481908d49e5393e3dff28 |
completed | May 22, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 21, 2026, 9:08 p.m.