Triple
T35858618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish community of Hebron |
E1036577
|
entity |
| Predicate | wasReestablishedIn |
P9113
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Jewish community of Hebron, wasReestablishedIn, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReestablishedIn Context triple: [Jewish community of Hebron, wasReestablishedIn, 1967]
-
A.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
B.
reestablishedCountry
Indicates that an entity restored or re-founded a country that had previously ceased to exist or lost its prior status.
-
C.
re-establishedOn
Indicates that a previously existing relationship, status, or entity was restored or brought back into effect on a specific date or time.
-
D.
laterRefoundedAs
Indicates that an entity was dissolved or ceased to exist and was subsequently re-established under a new or modified form, identity, or organization.
-
E.
reestablishedInCentury
Indicates that an entity, previously established and then discontinued or disrupted, was re-founded or restored during a specified century.
- 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.