Triple
T27050250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzie Q |
E684744
|
entity |
| Predicate | hasTitleSpellingVariant |
P457
|
FINISHED |
| Object | Susie Q |
—
|
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: Susie Q | Statement: [Suzie Q, hasTitleSpellingVariant, Susie Q]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleSpellingVariant Context triple: [Suzie Q, hasTitleSpellingVariant, Susie Q]
-
A.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
B.
hasWorkTitleVariant
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
C.
hasTitleInEnglishOrthography
Indicates that an entity has a specific title expressed using English spelling and writing conventions.
-
D.
spellingOfNameInTitle
Indicates that the specific spelling of a person's or entity's name appears in the title of a work or resource.
-
E.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 8:13 a.m.