Triple
T34789554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwitzer |
E1002908
|
entity |
| Predicate | hasVariantOrRelatedForm |
P455
|
FINISHED |
| Object | Schweitzer |
—
|
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: Schweitzer | Statement: [Schwitzer, hasVariantOrRelatedForm, Schweitzer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantOrRelatedForm Context triple: [Schwitzer, hasVariantOrRelatedForm, Schweitzer]
-
A.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
C.
hasVariantSeries
Indicates a relationship where one entity is a variant or alternative series derived from or associated with another series.
-
D.
hasVariantFamily
Indicates that one entity is related to another as a different version, type, or family variant of it.
-
E.
hasVariantIdentifications
Indicates that an entity is associated with one or more alternative identifications or versions that differ in some defined way from a primary identification.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.