Triple
T9336849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Currie |
E224665
|
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: [Arthur Currie, familyName, Currie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Currie Context triple: [Arthur Currie, familyName, Currie]
-
A.
Currie
Currie is a suburban village on the outskirts of Edinburgh, Scotland, known for its historic character and location along the Water of Leith.
-
B.
Currie
Currie is the principal township and administrative center of King Island in the Bass Strait, Tasmania, Australia.
-
C.
Currie
chosen
Currie is a Scottish-origin surname borne by various notable individuals across fields such as military, politics, and the arts.
-
D.
Seddon
Seddon is a small rural town in New Zealand’s Marlborough region, known for its surrounding vineyards and proximity to the Awatere Valley wine-growing area.
-
E.
Curran
Curran is a surname of Irish origin borne by various notable individuals in politics, sports, 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37f161e481908e23c1ec7e5fcf97 |
completed | April 1, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0e3d8316081908cb9ea36eb069c2d |
completed | April 4, 2026, 10:11 a.m. |
Created at: March 30, 2026, 7:40 p.m.