Triple
T6173366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yosef |
E137757
|
entity |
| Predicate | isCommonInCommunity |
P5924
|
FINISHED |
| Object | Jewish communities |
—
|
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 communities | Statement: [Yosef, isCommonInCommunity, Jewish communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonInCommunity Context triple: [Yosef, isCommonInCommunity, Jewish communities]
-
A.
isCommunityOf
Indicates that one entity functions as a community composed of, or defined by, the members or elements represented by the other entity.
-
B.
usedInCommunity
chosen
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
E.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.