Triple
T9948191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holworthy |
E195258
|
entity |
| Predicate | spellingVariantStatus |
P457
|
FINISHED |
| Object | no widely known common variants |
—
|
LITERAL 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: no widely known common variants | Statement: [Holworthy, spellingVariantStatus, no widely known common variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spellingVariantStatus Context triple: [Holworthy, spellingVariantStatus, no widely known common variants]
-
A.
spellingStatus
Indicates the correctness or condition of the spelling of a given text or term.
-
B.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
spellingStyle
Indicates the particular orthographic convention or system of spelling that is used or preferred in a given context.
-
E.
hasOrthographyStatus
Indicates the orthographic status or condition of how something is written or spelled, such as its conformity to a particular writing system or standard.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb659307c81908279adb641ceef86 |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.