Triple
T12473791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Macaulay Trevelyan |
E298125
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Trevelyan |
E912188
|
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: Trevelyan | Statement: [George Macaulay Trevelyan, familyName, Trevelyan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trevelyan Context triple: [George Macaulay Trevelyan, familyName, Trevelyan]
-
A.
Trevelyan
chosen
Trevelyan is an English surname historically associated with several notable British families, politicians, and literary figures.
-
B.
Brenan
Brenan is a given name and surname that serves as a spelling variant of Brennen.
-
C.
Southery
Southery is a village and civil parish in Norfolk, England, situated in the Fens near the River Great Ouse.
-
D.
Cunlhat
Cunlhat is a small rural commune in central France’s Puy-de-Dôme department, known for its traditional Auvergne countryside setting.
-
E.
Dalrymple
Dalrymple is a surname most notably associated with several Scottish nobles, politicians, and writers across history.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dca022c819082138fd4d08516da |
completed | April 10, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63f2373308190b41aafa635c8de5e |
completed | May 2, 2026, 6:14 p.m. |
Created at: April 8, 2026, 9:56 p.m.