Triple
T17790214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ouse (Sussex) |
E444137
|
entity |
| Predicate | nameDistinguishingNote |
P117526
|
FINISHED |
| Object | distinct from River Great Ouse |
—
|
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: distinct from River Great Ouse | Statement: [River Ouse (Sussex), nameDistinguishingNote, distinct from River Great Ouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameDistinguishingNote Context triple: [River Ouse (Sussex), nameDistinguishingNote, distinct from River Great Ouse]
-
A.
nameDistinction
chosen
Indicates that two entities are distinguished from one another specifically by differences in their names.
-
B.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
C.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
D.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
E.
isDistinctiveGivenNameOf
Indicates that a given name uniquely and distinctively identifies or characterizes a particular entity compared to others.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879688908190a5428b1fa7525f62 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.