Triple
T38374019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandlar |
E893566
|
entity |
| Predicate | isVariantSpellingUsedAs |
P457
|
FINISHED |
| Object | first name |
—
|
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: first name | Statement: [Chandlar, isVariantSpellingUsedAs, first name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVariantSpellingUsedAs Context triple: [Chandlar, isVariantSpellingUsedAs, first name]
-
A.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
B.
spellingVariantPattern
Indicates a relationship where one form of a word is a systematic spelling variant of another, following a recognizable pattern of orthographic change.
-
C.
hasSpellingVariantFrequency
Indicates a relationship where one spelling variant of a term is associated with how often it occurs relative to other variants.
-
D.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
E.
isSometimesUsedAsVariantOf
Indicates that one entity is occasionally employed as an alternative or substitute form of another entity, but not as its primary or standard version.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.