Triple
T11715860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phyllis Fraser |
E278495
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Fraser |
E254434
|
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: Fraser | Statement: [Phyllis Fraser, familyName, Fraser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fraser Context triple: [Phyllis Fraser, familyName, Fraser]
-
A.
Fraser
Fraser is a small mountain town in Colorado known for its proximity to ski resorts and outdoor recreation in the Rocky Mountains.
-
B.
Fraser
Fraser is a residential suburb in the Belconnen district of Canberra, in the Australian Capital Territory.
-
C.
Fraser
chosen
Fraser is a common Scottish surname historically associated with the Clan Fraser and borne by many notable figures worldwide.
-
D.
Kinnaird
Kinnaird is a historic Scottish estate and locality traditionally associated with the Carnegie family and the title of Lord Carnegie of Kinnaird.
-
E.
Fraser of Philorth
Fraser of Philorth is a prominent cadet branch of the Scottish Clan Fraser historically associated with the lands around Philorth in Aberdeenshire.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4bf54d88190a8e07fbbf8d9e962 |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef8397a4ac8190a71dfdd53bfa168a |
completed | April 27, 2026, 3:41 p.m. |
Created at: April 8, 2026, 9:40 p.m.