Triple
T21071318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norman Lockyer |
E519113
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lockyer |
—
|
NE NERFINISHED |
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: Lockyer | Statement: [Norman Lockyer, familyName, Lockyer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lockyer Context triple: [Norman Lockyer, familyName, Lockyer]
-
A.
Lockyer
chosen
Lockyer is an electoral district of the Queensland Legislative Assembly in Australia, covering rural and semi-rural communities in the Lockyer Valley region.
-
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.
Ryen
Ryen is a residential neighborhood in Oslo, Norway, known for its apartment blocks, local amenities, and good public transport connections.
-
D.
Shriever
Shriever is a surname, a variant spelling of "Shriver," borne by various individuals of English-speaking origin.
-
E.
Scarphe
Scarphe is a figure from Greek mythology known primarily as the wife of Aeson, the father of the hero Jason.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb8ed4481909c9f804ccd8da3e2 |
completed | April 21, 2026, 4:36 a.m. |
Created at: April 16, 2026, 2:46 p.m.