Triple
T7675442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkenazi surnames |
E173849
|
entity |
| Predicate | commonSuffix |
P42400
|
FINISHED |
| Object | -berg |
—
|
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: -berg | Statement: [Ashkenazi surnames, commonSuffix, -berg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSuffix Context triple: [Ashkenazi surnames, commonSuffix, -berg]
-
A.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
B.
usedAsSuffixTo
chosen
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
C.
blendsWith
Indicates that one entity can be mixed or combined smoothly with another to form a uniform or harmonious result.
-
D.
sharesCommonAncestorWith
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
E.
endsWith
Indicates that one entity terminates with, or has as its final part, the sequence or element represented by the other 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.