Triple
T31493045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isis (Oxford reach of the River Thames) |
E803457
|
entity |
| Predicate | isNameUsedBy |
P2937
|
FINISHED |
| Object | Oxford residents |
—
|
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: Oxford residents | Statement: [Isis (Oxford reach of the River Thames), isNameUsedBy, Oxford residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNameUsedBy Context triple: [Isis (Oxford reach of the River Thames), isNameUsedBy, Oxford residents]
-
A.
nameUsedBy
chosen
Indicates that a particular name is employed or referenced by a specific entity.
-
B.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
C.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
D.
nameUsedBefore
Indicates that a particular name has been used or referenced at an earlier time or in a prior context relative to the current one.
-
E.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e657248190a11fc2bb49c9548a |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:39 p.m.