Triple
T13854045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southampton F.C. |
E333015
|
entity |
| Predicate | commonName |
P570
|
FINISHED |
| Object | Saints |
E333015
|
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: Saints | Statement: [Southampton F.C., commonName, Saints]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saints Context triple: [Southampton F.C., commonName, Saints]
-
A.
Saints
The Saints are the athletic teams and mascot identity representing Aquinas College in collegiate sports and campus activities.
-
B.
Saints
The Saints are the athletic teams and mascot identity representing Presentation College in collegiate sports.
-
C.
Saints
chosen
Saints is the common nickname for Southampton Football Club, an English professional football team based in Southampton that competes in the English football league system.
-
D.
Saints
The Saints are the athletic teams representing Siena College in intercollegiate sports.
-
E.
Saints
Saints is the commonly used nickname for St Helens R.F.C., a prominent professional rugby league club based in St Helens, Merseyside, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02db9c9c81909bb2d2fbfb7394b1 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c70a59e8819090b750699993a107 |
completed | May 3, 2026, 10:07 p.m. |
Created at: April 9, 2026, 10:14 p.m.