Triple
T202092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sephardi Jews |
E4526
|
entity |
| Predicate | majorCommunity |
P2321
|
FINISHED |
| Object | Sephardi Jews in Morocco |
—
|
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: Sephardi Jews in Morocco | Statement: [Sephardi Jews, majorCommunity, Sephardi Jews in Morocco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCommunity Context triple: [Sephardi Jews, majorCommunity, Sephardi Jews in Morocco]
-
A.
hasMajorCommunity
chosen
Indicates that an entity possesses a primary or significantly large community associated with it.
-
B.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
largestCommunityIn
Indicates that one community is the largest (by some defined measure, such as population or size) among all communities within a given area or entity.
-
D.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
E.
notableCityCommunity
Indicates a relationship where a city is notably associated with, recognized by, or significantly connected to a particular 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.