Triple
T7570708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Ramsay |
E179230
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ramsay |
E267423
|
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: Ramsay | Statement: [William Ramsay, familyName, Ramsay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ramsay Context triple: [William Ramsay, familyName, Ramsay]
-
A.
Ramsay
chosen
Ramsay is a Scottish-origin surname borne by numerous notable figures in British history, including military leaders, politicians, and artists.
-
B.
Ewart
Ewart is a given name notably borne by the 19th-century British statesman William Ewart Gladstone.
-
C.
Ruthven
Ruthven is a Scottish noble family name historically associated with influential aristocrats and political figures in Scotland.
-
D.
Ruthven
Ruthven is a suburban railway station in Melbourne, Australia, serving the local community on the metropolitan train network.
-
E.
Paton
Paton is a surname and given name of Scottish origin, used by various notable individuals in fields such as sports, politics, and the arts.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f920540c8190817712db5aa3eeff |
completed | March 27, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c856e475348190a7c1e9872b513899 |
completed | March 28, 2026, 10:32 p.m. |
Created at: March 27, 2026, 3:51 p.m.