Triple
T3251809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churban |
E68198
|
entity |
| Predicate | extendsByAnalogyTo |
P36561
|
FINISHED |
| Object | later Jewish persecutions |
—
|
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: later Jewish persecutions | Statement: [Churban, extendsByAnalogyTo, later Jewish persecutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsByAnalogyTo Context triple: [Churban, extendsByAnalogyTo, later Jewish persecutions]
-
A.
viewOnAnalogy
chosen
Indicates a relationship where one entity interprets, understands, or evaluates another entity by drawing an analogy to something else.
-
B.
generalizationOf
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
-
C.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
D.
analogousTitle
Indicates that one entity has a title or position that corresponds in role, rank, or function to the title or position held by another entity.
-
E.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf425394819084ae6304da211c00 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.