Triple
T31493059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isis (Oxford reach of the River Thames) |
E803457
|
entity |
| Predicate | isAlsoNameOf |
P39
|
FINISHED |
| Object | Oxford University men’s second VIII (Isis crew) |
E1744593
|
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: Oxford University men’s second VIII (Isis crew) | Statement: [Isis (Oxford reach of the River Thames), isAlsoNameOf, Oxford University men’s second VIII (Isis crew)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlsoNameOf Context triple: [Isis (Oxford reach of the River Thames), isAlsoNameOf, Oxford University men’s second VIII (Isis crew)]
-
A.
isFormalNameOf
Indicates that one name is the official or formally recognized designation of an entity.
-
B.
alsoKnownAs
chosen
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
C.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
D.
isAliasOf
Indicates that one name, label, or identifier refers to the same entity as another.
-
E.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary one.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e657248190a11fc2bb49c9548a |
completed | May 3, 2026, 1:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b1466ce2c81909c2ef8ab108980f3 |
completed | June 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:39 p.m.