Triple
T26913167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoveniersstraat |
E677442
|
entity |
| Predicate | hasCommunityPresence |
P17132
|
FINISHED |
| Object | Jewish community |
—
|
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: Jewish community | Statement: [Hoveniersstraat, hasCommunityPresence, Jewish community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityPresence Context triple: [Hoveniersstraat, hasCommunityPresence, Jewish community]
-
A.
hasCommunityIn
chosen
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasOnlineCommunity
Indicates that an entity maintains or is associated with a community that interacts primarily through online platforms or digital channels.
-
C.
hasCommunitySpace
Indicates that an entity provides or includes a shared physical or virtual area intended for communal use, activities, or gatherings.
-
D.
hasCommunityLink
Indicates that there exists an established connection or association between an entity and a community.
-
E.
hasCommunityMedia
Indicates that an entity possesses, operates, or is associated with media outlets or channels that are created for and/or by a specific community.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 27, 2026, 6:03 a.m.