Triple
T5223993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephens |
E117939
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Stephenson |
E346930
|
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: Stephenson | Statement: [Stephens, hasVariant, Stephenson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stephenson Context triple: [Stephens, hasVariant, Stephenson]
-
A.
Stephenson
chosen
Stephenson is an English surname most famously associated with pioneering railway engineer George Stephenson and his son Robert.
-
B.
Humphreys
Humphreys is a small unincorporated community located within Lea County in southeastern New Mexico.
-
C.
Estey
Estey is a surname and place name most commonly associated with North American families and locations, sometimes appearing as a variant spelling of similar names like Easty.
-
D.
Michell
Michell is a given name and surname that functions as a variant spelling of Mitchell.
-
E.
Bonnell
Bonnell is the microarchitecture that underpinned Intel's first-generation Atom processors, designed for low-power, energy-efficient computing in mobile and embedded devices.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7abd3ed48190bfd8d2f2ca399741 |
completed | March 20, 2026, 4:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69beeff852bc81908467a343c5ded404 |
completed | March 21, 2026, 7:22 p.m. |
Created at: March 20, 2026, 1:48 p.m.