Triple
T4108477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rollie Lynn Riggs |
E88511
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Riggs |
E84786
|
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: Riggs | Statement: [Rollie Lynn Riggs, familyName, Riggs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riggs Context triple: [Rollie Lynn Riggs, familyName, Riggs]
-
A.
Riggs
chosen
Riggs is a surname most notably associated with American playwright Lynn Riggs, whose work inspired the musical "Oklahoma!".
-
B.
Eldridge
Eldridge is an English-language surname of Old English origin, borne by various notable individuals across fields such as politics, the arts, and sports.
-
C.
Shaughnessy
Shaughnessy is an affluent residential neighbourhood in Vancouver, British Columbia, known for its large heritage homes and tree-lined streets.
-
D.
McClure
McClure is a Scottish-origin surname borne by various notable individuals across fields such as exploration, politics, and the arts.
-
E.
Willard
Willard is a masculine given name of Old English origin meaning "resolute" or "strong-willed."
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af01da2b88819088a45401c0ec743a |
completed | March 9, 2026, 5:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b56b850d588190a0fc4b784bc7ca4f |
completed | March 14, 2026, 2:07 p.m. |
Created at: March 9, 2026, 3:40 p.m.