Triple
T29054179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קאוונא |
E735342
|
entity |
| Predicate | נחשבה ל |
P110882
|
FINISHED |
| Object | אחד המרכזים היהודיים החשובים בליטא |
—
|
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: אחד המרכזים היהודיים החשובים בליטא | Statement: [קאוונא, נחשבה ל, אחד המרכזים היהודיים החשובים בליטא]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: נחשבה ל Context triple: [קאוונא, נחשבה ל, אחד המרכזים היהודיים החשובים בליטא]
-
A.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
B.
נחשב
chosen
Indicates that something or someone is regarded, considered, or deemed to have a certain status, quality, or classification.
-
C.
couldConsider
Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
-
D.
alsoConsidered
Indicates that one item is regarded as an alternative or additional option alongside another in a given context.
-
E.
nowConsidered
Indicates that something has come to be regarded or classified in a particular way at the present time, possibly differing from how it was regarded before.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6609061508190ae12005d993e42bc |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:10 a.m.