Triple
T19706624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Thames at Oxford |
E473230
|
entity |
| Predicate | hasAlternativeNameOrigin |
P3325
|
FINISHED |
| Object | Latin name Isis from Thamesis |
—
|
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: Latin name Isis from Thamesis | Statement: [River Thames at Oxford, hasAlternativeNameOrigin, Latin name Isis from Thamesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeNameOrigin Context triple: [River Thames at Oxford, hasAlternativeNameOrigin, Latin name Isis from Thamesis]
-
A.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
B.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
C.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
hasAlternativeNameForSameRace
Indicates that one name is an alternative designation used for the same race as another name.
-
E.
hasAlternativeNameForSameCity
Indicates that one city name is an alternative or variant name referring to the same city as another name.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642bb5cd4819090e4c62bd74c4324 |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.