Triple
T21670784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxembourgish Jews |
E534837
|
entity |
| Predicate | reestablishedCommunityCentury |
P126521
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Luxembourgish Jews, reestablishedCommunityCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reestablishedCommunityCentury Context triple: [Luxembourgish Jews, reestablishedCommunityCentury, 19th century]
-
A.
reestablishedInCentury
chosen
Indicates that an entity, previously established and then discontinued or disrupted, was re-founded or restored during a specified century.
-
B.
foundedCommunity
Indicates that an entity established or created a community, organization, or group.
-
C.
reclamationStartCentury
Indicates the century in which a reclamation process or project began.
-
D.
reorganizedInCentury
Indicates that an entity underwent a significant reorganization or structural change during the specified century.
-
E.
reacquiredInCentury
Indicates that an entity was reacquired 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0badd08190ad2ec2b8e46be379 |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:37 p.m.