Triple
T7159932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewart |
E166915
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Ewart (surname) |
E166915
|
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: Ewart (surname) | Statement: [Ewart, relatedTo, Ewart (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ewart (surname) Context triple: [Ewart, relatedTo, Ewart (surname)]
-
A.
Ewart
chosen
Ewart is a given name notably borne by the 19th-century British statesman William Ewart Gladstone.
-
B.
Douglas (surname)
Douglas (surname) is a Scottish family name of Gaelic origin historically associated with a powerful Lowland clan and widely borne in English-speaking countries.
-
C.
Scott (surname)
Scott is a common English and Scottish surname historically associated with people from Scotland or of Scottish descent.
-
D.
Smith (surname)
Smith is a common English occupational surname originally denoting a metalworker or blacksmith.
-
E.
Hamilton (surname)
Hamilton is a common Scottish and English surname of Norman origin, borne by numerous notable figures in politics, science, and the arts.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e811d6b081909dafeee1d820c74f |
completed | March 27, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adc08b688190a00024727542c8b9 |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:47 p.m.