Triple
T35865437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Stevenson |
E1037072
|
entity |
| Predicate | mayAppearInRecordsUnderSpelling |
P457
|
FINISHED |
| Object | John Stephenson |
—
|
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: John Stephenson | Statement: [John Stevenson, mayAppearInRecordsUnderSpelling, John Stephenson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAppearInRecordsUnderSpelling Context triple: [John Stevenson, mayAppearInRecordsUnderSpelling, John Stephenson]
-
A.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
B.
spellingIncludes
Indicates that the spelling of one entity contains, as a substring or component, the spelling of another entity.
-
C.
spellingReplacedBy
Indicates that one spelling of a term has been superseded or substituted by another spelling.
-
D.
spellingVariantPattern
Indicates a relationship where one form of a word is a systematic spelling variant of another, following a recognizable pattern of orthographic change.
-
E.
sharesSpellingWith
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
- F. None of above.
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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.