Triple
T16021723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick S. Pardee |
E388613
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Pardee |
E635582
|
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: Pardee | Statement: [Frederick S. Pardee, familyName, Pardee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pardee Context triple: [Frederick S. Pardee, familyName, Pardee]
-
A.
Pardee
chosen
Pardee is a surname most notably associated with George Pardee, a Progressive-era governor of California and public health advocate.
-
B.
Doheny
Doheny is a surname most notably associated with Edward L. Doheny, an American oil tycoon and early petroleum industry pioneer.
-
C.
Tilghman
Tilghman is a masculine given name of English origin that has been borne by various notable American figures, including politicians and military officers.
-
D.
Leahey
Leahey is a surname variant of Leahy, an Irish family name of Gaelic origin.
-
E.
Dedridge
Dedridge is a residential neighbourhood within the new town of Livingston in West Lothian, 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18323fc0881908bab7126d9ccf67d |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf2c6128819091d8f3710578834e |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:55 a.m.