Triple
T11084716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. J. Cronin |
E262088
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Cronin |
E554642
|
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: Cronin | Statement: [A. J. Cronin, familyName, Cronin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cronin Context triple: [A. J. Cronin, familyName, Cronin]
-
A.
Cronin
chosen
Cronin is a surname of Irish origin borne by numerous notable individuals across sports, politics, literature, and the arts.
-
B.
Laird
Laird is a given name of Scottish origin traditionally used as a masculine middle or first name, associated with landownership and nobility.
-
C.
Crayke
Crayke is a small village and civil parish in North Yorkshire, England, known for its historic hilltop setting and views over the surrounding countryside.
-
D.
Dinneen
Dinneen is a surname of Irish origin borne by various notable individuals in sports, politics, and the arts.
-
E.
Shriever
Shriever is a surname, a variant spelling of "Shriver," borne by various individuals of English-speaking origin.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c0cc3081908448cfb26c08daf5 |
completed | April 9, 2026, 12:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e7a6dfa8819096f822294eb64dd1 |
completed | April 18, 2026, 8:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.