Triple
T30242767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larson |
E768962
|
entity |
| Predicate | hasTypicalSpellingInEnglish |
P56633
|
FINISHED |
| Object | Larson |
—
|
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: Larson | Statement: [Larson, hasTypicalSpellingInEnglish, Larson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSpellingInEnglish Context triple: [Larson, hasTypicalSpellingInEnglish, Larson]
-
A.
hasTypicalSpelling
chosen
Indicates that one form is the standard or commonly accepted spelling of another form.
-
B.
spellingStyle
Indicates the particular orthographic convention or system of spelling that is used or preferred in a given context.
-
C.
correspondsToEnglishSpelling
Indicates that one representation, form, or transcription matches or is equivalent to the standard English spelling of the same item.
-
D.
spellingStatus
Indicates the correctness or condition of the spelling of a given text or term.
-
E.
usesStandardOrthographyOf
Indicates that one entity writes or represents language according to the standard orthographic system defined for another entity.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 7:39 p.m.