Triple
T14015708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Thorpe |
E337198
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Thorpe |
E88398
|
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: Thorpe | Statement: [Jim Thorpe, familyName, Thorpe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Thorpe Context triple: [Jim Thorpe, familyName, Thorpe]
-
A.
Thorpe
chosen
Thorpe is an English surname most notably associated with Jeremy Thorpe, a prominent 20th-century British politician and former leader of the Liberal Party.
-
B.
Thorpe
Thorpe is a village in the English county of Surrey, located within the TW (Twickenham) postcode area.
-
C.
Thorpe, Derbyshire
Thorpe, Derbyshire is a small village in the Peak District of England, known as a popular base for walkers exploring the scenic Dovedale valley and surrounding countryside.
-
D.
Thorpe Cloud
Thorpe Cloud is a prominent limestone hill in the Peak District of England, known for its distinctive conical shape and panoramic views over Dovedale.
-
E.
Thorpe Ward
Thorpe Ward is a local electoral division that represents the Thorpe Bay area within its governing council.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbacac12608190a5e3d970ec3cda45 |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:19 p.m.