Triple
T9378665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Erskine |
E225720
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Erskine |
E99563
|
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: Erskine | Statement: [Peter Erskine, familyName, Erskine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Erskine Context triple: [Peter Erskine, familyName, Erskine]
-
A.
Erskine
chosen
Erskine is a masculine given name of Scottish origin, traditionally used as both a first name and a surname.
-
B.
Erskine
Erskine is a town in Renfrewshire, Scotland, situated on the southern bank of the River Clyde and known for the Erskine Bridge that connects it to West Dunbartonshire.
-
C.
Abernethy
Abernethy is a historic Scottish locality known for its early Christian monastic site and ancient Pictish heritage.
-
D.
Elphinstone
Elphinstone is a small village in East Lothian, Scotland, known for its rural character and proximity to the town of Tranent.
-
E.
Ruthven
Ruthven is a Scottish noble family name historically associated with influential aristocrats and political figures in Scotland.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50ac8aec8190a386c525e9cab7b1 |
completed | April 1, 2026, 5:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0f42a048081909012052e3dc77598 |
completed | April 4, 2026, 11:21 a.m. |
Created at: March 30, 2026, 7:44 p.m.