Triple
T8958546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Ewing |
E213539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century lawyer |
C887
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: 19th-century lawyer Context triple: [Charles Ewing, instanceOf, 19th-century lawyer]
-
A.
American lawyer
chosen
An American lawyer is a legal professional licensed in the United States who advises and represents clients in legal matters, interprets and applies U.S. laws, and advocates in courts and other legal settings.
-
B.
historical legal figure
A historical legal figure is an individual from the past whose work, decisions, or advocacy significantly influenced the development, interpretation, or practice of law.
-
C.
Scottish lawyer
A Scottish lawyer is a legal professional qualified in Scotland’s distinct legal system, advising and representing clients in civil or criminal matters before Scottish courts and tribunals.
-
D.
19th-century American businessman
A 19th-century American businessman is an entrepreneur or corporate leader who operated in the United States during the 1800s, typically engaged in industrial, commercial, or financial ventures shaped by rapid economic expansion, industrialization, and emerging national markets.
-
E.
English lawyer
An English lawyer is a legal professional qualified in the law of England and Wales who advises and represents clients in legal matters, either as a solicitor handling client relations and case preparation or as a barrister specializing in courtroom advocacy.
- F. None of above.
Provenance (1 batch)
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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7 p.m.