Triple
T34814055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Positive-Historical Judaism |
E1003578
|
entity |
| Predicate | originatedInPlace |
P3743
|
FINISHED |
| Object | Germany |
E1728
|
NE 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: Germany | Statement: [Positive-Historical Judaism, originatedInPlace, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedInPlace Context triple: [Positive-Historical Judaism, originatedInPlace, Germany]
-
A.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
B.
originatedAround
Indicates that something began, emerged, or came into existence approximately at a specified time or within a loosely defined period.
-
C.
originatedInNeighborhood
Indicates that an entity began, was founded, or first came into existence within a specific neighborhood.
-
D.
cityOfOriginal
Indicates the city from which something or someone originally comes or was first created or established.
-
E.
placeOfOrigin
chosen
Indicates the location or source from which an entity originally comes or was created.
- F. None of above.
Provenance (4 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a896ab648190a9e9d4b53b5c9a91 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.