Triple
T4645250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolff |
E101755
|
entity |
| Predicate | isSometimesOfAshkenaziOrigin |
P51397
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wolff, isSometimesOfAshkenaziOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSometimesOfAshkenaziOrigin Context triple: [Wolff, isSometimesOfAshkenaziOrigin, true]
-
A.
hasJewishSurnameUsage
Indicates that an entity uses or bears a surname that is of Jewish origin or commonly associated with Jewish heritage.
-
B.
hasMotherOrigin
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother entity.
-
C.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
D.
recognizedAsNationalityInCensusOf
Indicates that an entity was officially recorded or classified as having a particular nationality in the census conducted by a specified authority or at a specified time.
-
E.
ethnicAspect
chosen
Indicates a relationship where one entity reflects, involves, or characterizes the ethnic background, identity, or attributes of 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.