Triple
T6871297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin Currie |
E158551
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Currie |
E224665
|
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: Currie | Statement: [Austin Currie, familyName, Currie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Currie Context triple: [Austin Currie, familyName, Currie]
-
A.
Currie
chosen
Currie is a Scottish-origin surname borne by various notable individuals across fields such as military, politics, and the arts.
-
B.
Currie
Currie is a suburban village on the outskirts of Edinburgh, Scotland, known for its historic character and location along the Water of Leith.
-
C.
Currie
Currie is the principal township and administrative center of King Island in the Bass Strait, Tasmania, Australia.
-
D.
Curran
Curran is a surname of Irish origin borne by various notable individuals in politics, sports, and the arts.
-
E.
Gleeson
Gleeson is an Irish surname most prominently associated with acclaimed actor Brendan Gleeson and his family of performers.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8ac04e08190aa8011c0ade9d509 |
completed | March 27, 2026, 7:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742a841548190abd706ea1efd622f |
completed | March 28, 2026, 2:53 a.m. |
Created at: March 27, 2026, 2:22 p.m.